[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <117191397.rLtE3Es1ot@tauon.chronox.de>
Date: Wed, 11 Apr 2018 14:59:59 +0200
From: Stephan Mueller <smueller@...onox.de>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: "Theodore Y. Ts'o" <tytso@....edu>,
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 <syzkaller-bugs@...glegroups.com>,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH] crypto: DRBG - guard uninstantion by lock
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
Powered by blists - more mailing lists