From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Stephan Müller" <smueller@chronox.de>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Matthew Wilcox <willy@infradead.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>,
linux-crypto@vger.kernel.org, Eric Biggers <ebiggers3@gmail.com>,
syzbot <syzbot+75397ee3df5c70164154@syzkaller.appspotmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs@googlegroups.com,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] crypto: DRBG - guard uninstantion by lock
Date: Sun, 8 Apr 2018 18:46:03 -0400 [thread overview]
Message-ID: <20180408224603.GA32004@thunk.org> (raw)
In-Reply-To: <6541596.TtyMCBNA0Q@positron.chronox.de>
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
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Stephan Müller" <smueller@chronox.de>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Matthew Wilcox <willy@infradead.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>,
linux-crypto@vger.kernel.org, Eric Biggers <ebiggers3@gmail.com>,
syzbot <syzbot+75397ee3df5c70164154@syzkaller.appspotmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs@googlegroups.com,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] crypto: DRBG - guard uninstantion by lock
Date: Sun, 8 Apr 2018 18:46:03 -0400 [thread overview]
Message-ID: <20180408224603.GA32004@thunk.org> (raw)
In-Reply-To: <6541596.TtyMCBNA0Q@positron.chronox.de>
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
next prev parent reply other threads:[~2018-04-08 22:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 13:24 WARNING in kmem_cache_free syzbot
2018-04-06 13:33 ` Dmitry Vyukov
2018-04-08 3:16 ` Use struct page for filename Matthew Wilcox
2018-04-08 4:42 ` Al Viro
2018-04-08 5:59 ` WARNING in kmem_cache_free Al Viro
2018-04-08 6:01 ` Matthew Wilcox
2018-04-08 10:26 ` Dmitry Vyukov
2018-04-08 11:18 ` Dmitry Vyukov
2018-04-08 15:31 ` Stephan Müller
2018-04-08 15:41 ` Dmitry Vyukov
2018-04-08 19:07 ` [PATCH] crypto: DRBG - guard uninstantion by lock Stephan Müller
2018-04-08 22:46 ` Theodore Y. Ts'o [this message]
2018-04-08 22:46 ` Theodore Y. Ts'o
2018-04-09 5:40 ` Stephan Mueller
2018-04-09 7:57 ` Dmitry Vyukov
2018-04-10 15:23 ` Dmitry Vyukov
2018-04-10 15:35 ` Stephan Mueller
2018-04-11 12:29 ` Dmitry Vyukov
2018-04-11 12:59 ` Stephan Mueller
2018-04-11 14:26 ` Stephan Müller
2018-04-11 14:31 ` [PATCH] crypto: drbg - set freed buffers to NULL Stephan Müller
2018-04-11 17:29 ` Eric Biggers
2018-04-11 17:29 ` Eric Biggers
2018-04-12 6:40 ` Stephan Müller
2018-04-20 16:54 ` Herbert Xu
2018-04-20 16:54 ` Herbert Xu
2018-04-11 17:09 ` [PATCH] crypto: DRBG - guard uninstantion by lock Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180408224603.GA32004@thunk.org \
--to=tytso@mit.edu \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=ebiggers3@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.de \
--cc=syzbot+75397ee3df5c70164154@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.