aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndrey Konovalov <andreyknvl@google.com>2020-02-19 13:14:38 +0100
committerGitHub <noreply@github.com>2020-02-19 13:14:38 +0100
commitb4e5deb4365ee0e678d831030cc957609ab27f91 (patch)
tree2e028537fd7e992ce159996dfd537629639a0a74
parent135c18aadb0147f93d3e2658e42fc7a479b9ad04 (diff)
Update syzbot.md
-rw-r--r--docs/syzbot.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/syzbot.md b/docs/syzbot.md
index 63129c4a1..22a9c9543 100644
--- a/docs/syzbot.md
+++ b/docs/syzbot.md
@@ -82,12 +82,14 @@ or to check if the bug is already fixed by some recent commit.
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
+**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: see [below](#kmsan-bugs) for `KMSAN` bugs testing.
+**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.
-Note: see [below](#usb-bugs) for `USB` bugs testing.
+**Note**: see [below](#kmsan-bugs) for `KMSAN` bugs testing.
+
+**Note**: see [below](#usb-bugs) for `USB` bugs testing.
<div id="amend"/>
<div id="linux-next"/>