From b690a6e3360b20e5cbb9fd419a47382281b0d01f Mon Sep 17 00:00:00 2001 From: Andrey Konovalov Date: Wed, 19 Feb 2020 14:11:29 +0100 Subject: Update syzbot.md --- docs/syzbot.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/syzbot.md b/docs/syzbot.md index 0b57bde67..1a0ee182e 100644 --- a/docs/syzbot.md +++ b/docs/syzbot.md @@ -85,7 +85,12 @@ After sending an email you should get a reply email with results within an hour. **Note**: you may send the request only to `syzbot` email address, as patches sent to some mailing lists (e.g. netdev, netfilter-devel) will trigger patchwork. -**Note**: when testing a patch, syzbot uses the kernel config and reproducer that are specified a the initial bug report. As a result, specifying a repo, branch or commit id that are different from the ones that were used for reproducing, can result in false-positive Tested-by responses. For example this happens, when the bug is no longer reproducible on a specified kernel tree, with or without the supplied patch. +**Note**: when testing a patch, syzbot uses the newest reproducer and the matching +kernel config that are listed on the dashboard for this bug. As a result, specifying +a repo, branch or commit id that are different from the ones that were used for +reproducing, can result in false-positive Tested-by responses. For example this +happens, when the bug is not reproducible on a specified kernel tree, with or without +the supplied patch. **Note**: see [below](#kmsan-bugs) for `KMSAN` bugs testing. @@ -331,8 +336,8 @@ the following line: #syz test: https://github.com/google/kasan.git commit-hash ``` and attach/inline your test patch in the same email. `commit-hash` is the id -of the kernel commit on which this bug was reproduced, its value can be found -in the initial report email. +of the kernel commit that corresponds to the **newest reproducer** listed on +the dashboard for this bug. If the bug was triggered on the `KMSAN` tree, follow the [instructions above](#kmsan-bugs), with the exception that you must also use `commit-hash` instead of the `master` -- cgit mrf-deployment