aboutsummaryrefslogtreecommitdiffstats
path: root/docs/syzbot.md
diff options
context:
space:
mode:
authorAndrey Konovalov <andreyknvl@google.com>2020-02-19 13:20:36 +0100
committerGitHub <noreply@github.com>2020-02-19 13:20:36 +0100
commit47fae6e9224612a0d0b40f2e39a79323e19855bf (patch)
treede60ec253c3ded86352ed32a39dc38c11939e2ba /docs/syzbot.md
parentb4e5deb4365ee0e678d831030cc957609ab27f91 (diff)
Update syzbot.md
Diffstat (limited to 'docs/syzbot.md')
-rw-r--r--docs/syzbot.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/syzbot.md b/docs/syzbot.md
index 22a9c9543..0b57bde67 100644
--- a/docs/syzbot.md
+++ b/docs/syzbot.md
@@ -85,7 +85,7 @@ 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.
+**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**: see [below](#kmsan-bugs) for `KMSAN` bugs testing.