Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dashboard/app: close fix-bisected bugs as fixed rather than obsolete #5318

Open
dvyukov opened this issue Sep 16, 2024 · 1 comment
Open

Comments

@dvyukov
Copy link
Collaborator

dvyukov commented Sep 16, 2024

"WARNING in cow_file_range_inline" report:
https://syzkaller.appspot.com/bug?extid=858534c396b0cdd291d2
https://lore.kernel.org/all/[email protected]/

It was correctly fix-bisected, but then closed as obsolete. If it's indeed fixed, it's expected that it won't happen and will be closed as obsolete soon.
Since we don't systematically handle fix bisection results, I think it's more reasonable to close such bugs as fixed with the commit (at the time it would be currently obsoleted, to give any human moderators time to act).

@dvyukov
Copy link
Collaborator Author

dvyukov commented Sep 16, 2024

Another example where the same happened:
https://syzkaller.appspot.com/bug?extid=59a71007ccac79e8bb69

We could count how many such cases we have, and potentially fix up the data base.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant