[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180429121745.6csnvc2jjay6ozfc@wfg-t540p.sh.intel.com>
Date: Sun, 29 Apr 2018 20:17:45 +0800
From: Fengguang Wu <fengguang.wu@...el.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Theodore Ts'o <tytso@....edu>,
"Jason A. Donenfeld" <Jason@...c4.com>, LKP <lkp@...org>,
gkohli@...eaurora.org
Subject: Re: [crng_reseed] WARNING: inconsistent lock state
On Sun, Apr 29, 2018 at 03:07:06AM +0000, Linus Torvalds wrote:
>On Sat, Apr 28, 2018 at 7:26 PM Fengguang Wu <fengguang.wu@...el.com> wrote:
>
>> FYI this happens in mainline kernel 4.17.0-rc2.
>> It looks like a new regression.
>
>> It occurs in 3 out of 3 boots.
>
>> There is another "[ 294.642506] BUG: sleeping function called from
>> invalid context at mm/slab.h:421" at the bottom of this long dmesg:
>
>This should be fixed by commit 6c1e851c4edc ("random: fix possible sleeping
>allocation from irq context").
Yes that fixes the bug. Sorry for the late report!
Regards,
Fengguang
Powered by blists - more mailing lists