From: Peter Zijlstra <peterz@infradead.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: syzbot <syzbot+d5b23b18d2f4feae8a67@syzkaller.appspotmail.com>,
bristot@redhat.com, bsegall@google.com, dietmar.eggemann@arm.com,
gor@linux.ibm.com, jgross@suse.com, juri.lelli@redhat.com,
linux-kernel@vger.kernel.org, mgorman@suse.de, mingo@kernel.org,
mingo@redhat.com, namit@vmware.com, rdunlap@infradead.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com,
vincent.guittot@linaro.org
Subject: Re: [syzbot] possible deadlock in wake_up_all_idle_cpus
Date: Tue, 19 Oct 2021 22:27:41 +0200 [thread overview]
Message-ID: <20211019202741.GN174703@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20211019190811.ubam63tfv33c7lmx@linutronix.de>
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.
next prev parent reply other threads:[~2021-10-19 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 16:51 [syzbot] possible deadlock in wake_up_all_idle_cpus syzbot
2021-10-16 18:07 ` syzbot
2021-10-16 23:32 ` syzbot
2021-10-19 19:08 ` Sebastian Andrzej Siewior
2021-10-19 20:27 ` Peter Zijlstra [this message]
2021-10-20 6:32 ` Sebastian Andrzej Siewior
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=20211019202741.GN174703@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gor@linux.ibm.com \
--cc=jgross@suse.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namit@vmware.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzbot+d5b23b18d2f4feae8a67@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vincent.guittot@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.