[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <58C3C45A-1C05-4900-B82D-5AAF7538B9C8@lca.pw>
Date: Mon, 13 Jan 2020 08:42:55 -0500
From: Qian Cai <cai@....pw>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
"Steven Rostedt (VMware)" <rostedt@...dmis.org>,
bsegall@...gle.com, mgorman@...e.de, paulmck@...nel.org,
tglx@...utronix.de, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched/core: fix illegal RCU from offline CPUs
> On Jan 13, 2020, at 3:22 AM, Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp> wrote:
>
> Is commit 7283094ec3db318e ("kernel, oom: fix potential pgd_lock deadlock from
> __mmdrop") about only softirq? Is it guaranteed that smp_call_function_single()
> does not hit such race? Then just my overcareful...
That commit looks like a different issue. We are not call mmdrop() from softirq here.
Powered by blists - more mailing lists