[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YgiEeHzz4JZFszJD@casper.infradead.org>
Date: Sun, 13 Feb 2022 04:09:28 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Zhouyi Zhou <zhouzhouyi@...il.com>
Cc: Paul Menzel <pmenzel@...gen.mpg.de>,
Michael Ellerman <mpe@...erman.id.au>,
linuxppc-dev@...ts.ozlabs.org, Linux-MM <linux-mm@...ck.org>,
Peter Zijlstra <peterz@...radead.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Jason Baron <jbaron@...mai.com>, rcu <rcu@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
"Paul E. McKenney" <paulmck@...nel.org>
Subject: Re: BUG: sleeping function called from invalid context at
include/linux/sched/mm.h:256
On Sun, Feb 13, 2022 at 11:19:09AM +0800, Zhouyi Zhou wrote:
> I think the key to the problem lies in your attached console.log
> (pasted below), at times 0.014987 and 0.015995, I see there are two
> locks (cpu_hotplug_lock and jump_label_mutex) holded while
> kmem_cache_alloc calls __might_resched (0.023356).
Those are both sleeping locks (a percpu_rwsem and mutex, respectively).
There is no problem with sleeping while holding a mutex or rwsem.
Powered by blists - more mailing lists