From: Jens Axboe <axboe@kernel.dk>
To: Matthew Wilcox <willy@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Lameter <cl@linux.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: slub: BUG: Invalid wait context
Date: Thu, 2 Sep 2021 13:05:31 -0600 [thread overview]
Message-ID: <4b884d2b-bcac-4967-d792-f7653084c38d@kernel.dk> (raw)
In-Reply-To: <YTEf2MEkEdMVAuRF@casper.infradead.org>
On 9/2/21 1:02 PM, Matthew Wilcox wrote:
> On Thu, Sep 02, 2021 at 12:59:33PM -0600, Jens Axboe wrote:
>> On 9/2/21 12:56 PM, Matthew Wilcox wrote:
>>> On Thu, Sep 02, 2021 at 10:22:23AM -0600, Jens Axboe wrote:
>>>> Hi,
>>>>
>>>> Booting current -git yields the below splat. I'm assuming this is
>>>> related to the new RT stuff, where spin_lock() can sleep. This obviously
>>>> won't fly off IPI.
>>>
>>> You want to turn off PROVE_RAW_LOCK_NESTING for the moment.
>>
>> Because?
>
> help
> Enable the raw_spinlock vs. spinlock nesting checks which ensure
> that the lock nesting rules for PREEMPT_RT enabled kernels are
> not violated.
>
> NOTE: There are known nesting problems. So if you enable this
> option expect lockdep splats until these problems have been fully
> addressed which is work in progress. This config switch allows to
> identify and analyze these problems. It will be removed and the
> check permanently enabled once the main issues have been fixed.
>
> If unsure, select N.
This isn't a new text, it's been like that for quite a while. The warning
is new on -git with that option.
--
Jens Axboe
next prev parent reply other threads:[~2021-09-02 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 16:22 Jens Axboe
2021-09-02 18:56 ` Matthew Wilcox
2021-09-02 18:59 ` Jens Axboe
2021-09-02 19:02 ` Matthew Wilcox
2021-09-02 19:05 ` Jens Axboe [this message]
2021-09-02 19:55 ` Thomas Gleixner
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=4b884d2b-bcac-4967-d792-f7653084c38d@kernel.dk \
--to=axboe@kernel.dk \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tglx@linutronix.de \
--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