linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Zqiang <qiang.zhang@windriver.com>,
	Kees Cook <keescook@chromium.org>,
	Stephen Boyd <swboyd@chromium.org>, Tejun Heo <tj@kernel.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: [5.14] problem with dynamic memory allocation for object debugging
Date: Sun, 15 Aug 2021 11:42:00 +0100	[thread overview]
Message-ID: <YRjveNu9NDcIzCGg@casper.infradead.org> (raw)
In-Reply-To: <b9cadd1b-ed1f-8eab-5de5-36c79c709c67@i-love.sakura.ne.jp>

On Sun, Aug 15, 2021 at 07:23:03PM +0900, Tetsuo Handa wrote:
> Hello.
> 
> I'm frequently hitting "BUG: Invalid wait context", and
> it seems that this problem is not fixed yet.
> 
> This is a problem between spinlock versus raw_spinlock. check_wait_context()
> complains if we try to take a spinlock when we already hold a raw_spinlock.

Disable this option:

config PROVE_RAW_LOCK_NESTING
        bool "Enable raw_spinlock - spinlock nesting checks"
        depends on PROVE_LOCKING
        default n
        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.

If you're not working on removing these splats yourself, then reporting
them has little value.


  reply	other threads:[~2021-08-15 10:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-15 10:23 [5.14] problem with dynamic memory allocation for object debugging Tetsuo Handa
2021-08-15 10:42 ` Matthew Wilcox [this message]
2021-08-16  9:10 ` Peter Zijlstra

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=YRjveNu9NDcIzCGg@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=boqun.feng@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-mm@kvack.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=peterz@infradead.org \
    --cc=qiang.zhang@windriver.com \
    --cc=swboyd@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).