[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20211020063230.r3cm2ubpmps3lcgo@linutronix.de>
Date: Wed, 20 Oct 2021 08:32:30 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Peter Zijlstra <peterz@...radead.org>
Cc: syzbot <syzbot+d5b23b18d2f4feae8a67@...kaller.appspotmail.com>,
bristot@...hat.com, bsegall@...gle.com, dietmar.eggemann@....com,
gor@...ux.ibm.com, jgross@...e.com, juri.lelli@...hat.com,
linux-kernel@...r.kernel.org, mgorman@...e.de, mingo@...nel.org,
mingo@...hat.com, namit@...are.com, rdunlap@...radead.org,
rostedt@...dmis.org, syzkaller-bugs@...glegroups.com,
vincent.guittot@...aro.org
Subject: Re: [syzbot] possible deadlock in wake_up_all_idle_cpus
On 2021-10-19 22:27:41 [+0200], Peter Zijlstra wrote:
> On Tue, Oct 19, 2021 at 09:08:11PM +0200, Sebastian Andrzej Siewior wrote:
> > Does this do anything useful?
>
> I've got https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?h=sched/core&id=3dfddc2f0f76525218dd2d0c8725d9f21dd411e2
>
> There's like 3 or 4 threads on this :/ I just got a tested-by on that.
Yeah I saw a few emails and wanted to talk to the bot, assuming it would
keep quiet then.
for_each_possible_cpu looks big but is probably equal to online_cpu in
most cases.
Thanks ;)
Sebastian
Powered by blists - more mailing lists