diff options
| author | Andrey Konovalov <andreyknvl@google.com> | 2019-07-29 15:22:36 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-07-29 15:22:36 +0200 |
| commit | f67095eefa21c9164a2a92062a04bf186a689d0a (patch) | |
| tree | 44e808dcc88f0a6dd36987765434c32fb96eab8c | |
| parent | c85e1c5be98819e885698b690ac15a8d05ae38a6 (diff) | |
Update syzbot.md
| -rw-r--r-- | docs/syzbot.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/syzbot.md b/docs/syzbot.md index 82117a04b..1395ab139 100644 --- a/docs/syzbot.md +++ b/docs/syzbot.md @@ -299,12 +299,13 @@ syzkaller has an ability to perform fuzzing of the Linux kernel USB stack, see the details [here](/docs/linux/external_fuzzing_usb.md). This requires non-yet-upstreamed kernel changes and thus patch testing is only possible on the `usb-fuzzer` branch of the `https://github.com/google/kasan.git` tree. -The standard way for triggering tests with the `usb-fuzzer` tree is to send an -email to `syzbot+HASH` address containing the following line: +The recommended way for triggering tests with the `usb-fuzzer` tree is to send +an email to `syzbot+HASH` address containing the following line: ``` -#syz test: https://github.com/google/kasan.git usb-fuzzer +#syz test: https://github.com/google/kasan.git commit-hash ``` -and attach/inline your test patch in the same email. +and attach/inline your test patch in the same email (`commit-hash` value can +be found in the initial report email). ## Memory leaks |