[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180424125541.GB4189@thunk.org>
Date: Tue, 24 Apr 2018 08:55:41 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: syzbot <syzbot+e1670f554caa60fb147b@...kaller.appspotmail.com>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
Henrik Rydberg <rydberg@...math.org>,
syzkaller-bugs@...glegroups.com
Subject: Re: WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
On Mon, Apr 23, 2018 at 10:49:12AM -0700, Dmitry Torokhov wrote:
> On Sun, Apr 22, 2018 at 7:02 PM, syzbot
> <syzbot+e1670f554caa60fb147b@...kaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot hit the following crash on upstream commit
> > 285848b0f4074f04ab606f1e5dca296482033d54 (Sun Apr 22 04:20:48 2018 +0000)
> > Merge tag 'random_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random
> > syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=e1670f554caa60fb147b
>
> Ted,
>
> input_add_randomness() (that ends up calling crng_reseed() and the new
> numa_crng_init()) is called (and has been called ever since inception)
> from an interrupt context and thus may not sleep. The following commit
> breaks this:
Fixed by: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1672186.html
Will be pushed to Linux shortly.
- Ted
Powered by blists - more mailing lists