Skip to content

Conversation

@a-nogikh
Copy link
Collaborator

@a-nogikh a-nogikh commented Jan 2, 2026

Apparently, the current timeout is not always enough in case of task hungs on a loaded VM:
https://groups.google.com/g/syzkaller-bugs/c/rI2gfkV02Ks

We only wait in case of crashes, so increasing the value should have a significant performance impact.

Apparently, the current timeout is not always enough in case of task
hungs on a loaded VM:
https://groups.google.com/g/syzkaller-bugs/c/rI2gfkV02Ks

We only wait in case of crashes, so increasing the value should have a
significant performance impact.
@a-nogikh a-nogikh requested a review from dvyukov January 2, 2026 22:15
@dvyukov
Copy link
Collaborator

dvyukov commented Jan 3, 2026

Do you think increasing wait will help? It printed no output for more than 5 seconds, and the output stops precisely at the start of the first stack, it did not print any at all. For me it suggests that more likely it deadlocked.

@a-nogikh
Copy link
Collaborator Author

Hmm, yes, sounds reasonable.

@a-nogikh a-nogikh closed this Jan 16, 2026
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