lists.openwall.net | 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 linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20180408224603.GA32004@thunk.org> Date: Sun, 8 Apr 2018 18:46:03 -0400 From: "Theodore Y. Ts'o" <tytso@....edu> To: Stephan Müller <smueller@...onox.de> Cc: Dmitry Vyukov <dvyukov@...gle.com>, Matthew Wilcox <willy@...radead.org>, Herbert Xu <herbert@...dor.apana.org.au>, David Miller <davem@...emloft.net>, linux-crypto@...r.kernel.org, Eric Biggers <ebiggers3@...il.com>, syzbot <syzbot+75397ee3df5c70164154@...kaller.appspotmail.com>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, syzkaller-bugs@...glegroups.com, Al Viro <viro@...iv.linux.org.uk> Subject: Re: [PATCH] crypto: DRBG - guard uninstantion by lock On Sun, Apr 08, 2018 at 09:07:03PM +0200, Stephan Müller wrote: > Can you please check whether the attached patch fixes the issue? > Stephan, FYI, if you incude in your e-mail "#syz test <GIT URL> <BRANCH>" as the first line of your patch and the syzbot e-mail is cc'ed, the syzbot will automatically apply the patch in the e-mail against the git tree/branch specified in the "#syz test" line, and then try to see if the problem it discovered still reproduces --- and then send you e-mail one way or another. So the syzbot will run while the patch goes through the normal e-mail review process, which is kind of neat. :-) Cheers, - Ted
Powered by blists - more mailing lists