Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20180429022606.267zucef42hm37m7@wfg-t540p.sh.intel.com>
In-Reply-To: <20180429022606.267zucef42hm37m7@wfg-t540p.sh.intel.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun, 29 Apr 2018 03:07:06 +0000
Message-ID: <CA+55aFwwsHmfn7i9TjQW73RYDctBdt4QBgyUG-OJ=+on_n0f_Q@mail.gmail.com>
Subject: Re: [crng_reseed] WARNING: inconsistent lock state
To:     Wu Fengguang <fengguang.wu@intel.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Arnd Bergmann <arnd@arndb.de>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        "Theodore Ts'o" <tytso@mit.edu>,
        "Jason A. Donenfeld" <Jason@zx2c4.com>, LKP <lkp@01.org>,
        gkohli@codeaurora.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sat, Apr 28, 2018 at 7:26 PM Fengguang Wu <fengguang.wu@intel.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").

                 Linus