From: Stephan Mueller <smueller@chronox.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
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 <syzkaller-bugs@googlegroups.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] crypto: DRBG - guard uninstantion by lock
Date: Wed, 11 Apr 2018 14:59:59 +0200 [thread overview]
Message-ID: <117191397.rLtE3Es1ot@tauon.chronox.de> (raw)
In-Reply-To: <CACT4Y+bRmYMt3WuVHE7e624KgRUTXQWa36wn-pr_gm2STq80bQ@mail.gmail.com>
Am Mittwoch, 11. April 2018, 14:29:45 CEST schrieb Dmitry Vyukov:
Hi Dmitry,
>
> What do you mean by description of the fault?
> It's kernel standard FAULT_INJECTION facility, it injects faults
> mainly into kmalloc/slab_alloc (also in a bunch of other things, but
> in this case this seems to be kmalloc). In the repro you can see that
> it's injecting a fault into 8-th malloc in the setsockopt syscall.
I am now able to reproduce it.
I think I have a smoking gun, but let me test it first.
Ciao
Stephan
next prev parent reply other threads:[~2018-04-11 13:00 UTC|newest]
Thread overview: 24+ 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
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 [this message]
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-12 6:40 ` Stephan Müller
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=117191397.rLtE3Es1ot@tauon.chronox.de \
--to=smueller@chronox.de \
--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=syzbot+75397ee3df5c70164154@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®