aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorDmitry Vyukov <dvyukov@google.com>2021-01-05 10:24:38 +0100
committerDmitry Vyukov <dvyukov@google.com>2021-01-05 10:52:40 +0100
commit684ed71721ff90d857544145848f427094869cc5 (patch)
treef515d7e67daf8beca544d253675ffff9b70c0130 /docs
parent2a28ff1f43e0081e6e080b26efc9efbe83b80539 (diff)
docs: clarify how syzbot identifies bugs
Diffstat (limited to 'docs')
-rw-r--r--docs/syzbot.md11
1 files changed, 9 insertions, 2 deletions
diff --git a/docs/syzbot.md b/docs/syzbot.md
index 959d86394..818c0835f 100644
--- a/docs/syzbot.md
+++ b/docs/syzbot.md
@@ -57,8 +57,15 @@ override the commit simply by sending another `#syz fix` command.
**Note**: all commands must start from beginning of the line.
-**Note**: please keep `syzkaller-bugs@googlegroups.com` mailing list in CC.
-It serves as a history of what happened with each bug report.
+**Note**: please keep at least `syzkaller-bugs@googlegroups.com` mailing list in CC.
+It serves as a history of what happened with each bug report. Keepint the main kernel
+mailing list (e.g. `linux-kernel@vger.kernel.org `) in CC is useful as well so that
+it's searchable in those archives as well.
+
+**Note**: `syzbot` identifies bugs by the `HASH` in the `syzbot+HASH@` receiver email address.
+So, strictly saying, you don't need to *reply* to emails (e.g. if you did not receive them),
+you can send a new email to the `syzbot+HASH@` email address, which you can find as `Sender`
+in email archives or as `Reported-by` email on the dashboard page for each bug.
<div id="testing-patches"/>