diff options
| author | Zubin Mithra <zsm@chromium.org> | 2019-09-03 11:09:04 -0700 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2019-09-18 15:09:15 +0200 |
| commit | 46c0be242e2548c889a96285e9c1ec97db28efe2 (patch) | |
| tree | fd40b057aa1c34a699a95548c9990a605e962e29 | |
| parent | 1037b424407669fb16fb435f4d839bde7717a791 (diff) | |
docs: update syzbot.md
Add in some information about fix bisection.
| -rw-r--r-- | docs/syzbot.md | 23 |
1 files changed, 22 insertions, 1 deletions
diff --git a/docs/syzbot.md b/docs/syzbot.md index d4426e979..5da87f0e1 100644 --- a/docs/syzbot.md +++ b/docs/syzbot.md @@ -164,7 +164,28 @@ so please treat the results with understanding. You may consult the provided Suggestions and patches that improve bisection quality for common cases are [welcome](https://github.com/google/syzkaller/issues/1051). -<div id="bisection"/> +`syzbot` supports cause bisection (find the commit that introduces a bug) and +fix bisection (find the commit that fixes a bug). + +The web UI for a specific kernel +(say [upstream linux](https://syzkaller.appspot.com/upstream)) shows the +`Bisected` status for all bugs. + +<div id="fix-bisection"/> + +### Fix bisection +`syzbot` will perform fix bisection on bugs that meet the following criterion: +- The kernel tree corresponding to the bug has fix bisection enabled (for +instance, fix bisection might be disabled on kernel trees that have commits +which are force pushed). +- The bug must have a reproducer. +- The bug must not have occurred for at least 30 days. If the bug still occurs +on HEAD upon fix bisection, it will be retried in another 30 days. + +If you receive an email with fix bisection results you think is correct, please +reply with a `#syz fix: commit-title` so that syzbot can close the bug report. + +<div id="syzkaller-reproducers"/> ## syzkaller reproducers |