Skip to content

Revert "Fuzz waitqueue instructions (#9012)" - #9230

Merged
stevenfontanella merged 1 commit into
mainfrom
revert
Oct 7, 2026
Merged

stevenfontanella merged 1 commit into
mainfrom
revert

Conversation

@stevenfontanella

@stevenfontanella stevenfontanella commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

Reverts #9012. The fuzzing code for waitqueues is correct but it exposes a bug with how waitqueues are handled in ctor-eval. Revert for now to disable fuzzing while the underlying issue is fixed. The only flag guarding waitqueue instructions is --shared-everything which we don't want to disable since it covers other features too.

Part of #8315.

@stevenfontanella
stevenfontanella marked this pull request as ready for review October 7, 2026 20:14
@stevenfontanella
stevenfontanella requested a review from a team as a code owner October 7, 2026 20:14
@stevenfontanella
stevenfontanella requested review from kripken and tlively and removed request for a team October 7, 2026 20:14

@kripken kripken left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm to revert, though if this is a matter of another day or two, waiting is also ok for me. (In my ping I mainly wanted to make sure this wasn't forgotten.)

AndInt32, arrayNew->size, builder.makeConst(int32_t(1024 - 1)));
}
}
if (!ATOMIC_WAITS) {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Side note, should this have been on FuzzParams and not on the main class?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess so. This was here before my PR (actually 9 years ago), and it looks like it's a compile-time constant; there's no code path that sets it to true.

I can see if we can refactor this part too.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, sorry, I thought it was part of the diff here...

@stevenfontanella

Copy link
Copy Markdown
Member Author

lgtm to revert, though if this is a matter of another day or two, waiting is also ok for me. (In my ping I mainly wanted to make sure this wasn't forgotten.)

Got it. I want to clean up some of the code as part of my fix anyway, so I'll revert to give us more time.

@stevenfontanella

Copy link
Copy Markdown
Member Author

Ran ~300k fuzzer iterations with no issues.

@stevenfontanella
stevenfontanella merged commit bee0b57 into main Oct 7, 2026
16 checks passed
@stevenfontanella
stevenfontanella deleted the revert branch October 7, 2026 22:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants