lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 21 Dec 2017 16:22:40 +0300
From:   Andrey Ryabinin <>
To:     Dmitry Vyukov <>
Cc:     LKML <>,
        syzkaller <>,
        Eric Dumazet <>,
        Eric Biggers <>,
        Kostya Serebryany <>,
        Alexander Potapenko <>,
        andreyknvl <>,
        Linus Torvalds <>,
        Greg Kroah-Hartman <>,
        Andrew Morton <>,
        Tetsuo Handa <>,
        David Miller <>,
        Willem de Bruijn <>,
        Guenter Roeck <>,
        Stephan Mueller <>
Subject: Re: [RFC] syzbot process

2017-12-21 15:52 GMT+03:00 Dmitry Vyukov <>:

> Any other proposals, thoughts, ideas?

a) Assume that patches send in replies to the bug report are fixes.

b) Almost the same as your "syzbot-fix: HASH"  proposal, but slightly
closer to normal kernel development workflow.
     Add hash/bug id into the From field of email, i.e.

     instead of
     From: syzbot <>

     make it
     From: syzbot-{hash} <>

     And ask to include "Reported-by: syzbot-{hash}
<>" tag in a changelog.

a) doesn't exclude b) or "#syz: fix " emails, and vise versa

Powered by blists - more mailing lists