Lines Matching refs:bug

12 `syzbot` needs to know when a bug is fixed in order to (1) verify that it is
14 (while a bug is considered open all similarly-looking crashes are merged into
15 the existing bug). To understand when a bug is fixed `syzbot` needs to know
16 what commit fixes the bug; once `syzbot` knows the commit it will track when
18 commit reaches all builds, the bug is considered closed (new similarly-looking
19 crashes create a new bug).
23 If you fix a bug reported by `syzbot`, please add the provided `Reported-by`
27 - to attach a fixing commit to the bug (if you forgot to add `Reported-by` tag):
36 - to mark the bug as a duplicate of another `syzbot` bug:
40 - to undo a previous dup command and turn it into an independent bug again:
44 - to mark the bug as a one-off invalid report (e.g. induced by a previous memory corruption):
48 **Note**: if the crash happens again, it will cause creation of a new bug report.
53 It serves as a history of what happened with each bug report.
59 code and testing with them), or to check if the bug still happens. To test on
75 or to check if the bug is already fixed by some recent commit.
101 … C reproducer, it wasn't able to trigger the bug using the C program (though, it can be just becau…
139 once it has one it adds it to the bug. If there is no reproducer referenced in a
140 bug, a reproducer does not exist. There are multiple reasons why `syzbot` can
162 which sends the bug to kernel mailing lists.
198 - it's hard to communicate exact state of the code with bug reports (not just hash anymore)