From: Tejun Heo <tj@kernel.org>
To: Qian Cai <cai@lca.pw>
Cc: Prateek Sood <prsood@codeaurora.org>,
Li Zefan <lizefan@huawei.com>,
cgroups@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: Deadlock due to "cpuset: Make cpuset hotplug synchronous"
Date: Fri, 3 Apr 2020 10:54:18 -0400 [thread overview]
Message-ID: <20200403145418.GB162390@mtj.duckdns.org> (raw)
In-Reply-To: <6AD62381-394F-4742-816B-12DE67DE9788@lca.pw>
On Wed, Apr 01, 2020 at 10:00:31PM -0400, Qian Cai wrote:
>
>
> > On Mar 25, 2020, at 3:19 PM, Tejun Heo <tj@kernel.org> wrote:
> >
> > On Wed, Mar 25, 2020 at 03:16:56PM -0400, Qian Cai wrote:
> >> The linux-next commit a49e4629b5ed (“cpuset: Make cpuset hotplug synchronous”)
> >> introduced real deadlocks with CPU hotplug as showed in the lockdep splat, since it is
> >> now making a relation from cpu_hotplug_lock —> cgroup_mutex.
> >
> > Prateek, can you please take a look? Given that the merge window is just around
> > the corner, we might have to revert and retry later if it can't be resolved
> > quickly.
>
> Tejun, can you back off this commit now given it seems nobody is trying to rescue it?
Yeah, gonna revert it before sending out the pull request.
Thanks.
--
tejun
next prev parent reply other threads:[~2020-04-03 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 19:16 Deadlock due to "cpuset: Make cpuset hotplug synchronous" Qian Cai
2020-03-25 19:19 ` Tejun Heo
2020-03-26 10:15 ` Qais Yousef
2020-04-03 14:55 ` Tejun Heo
2020-04-06 10:55 ` Qais Yousef
2020-04-06 14:34 ` Tejun Heo
2020-04-07 13:07 ` Qais Yousef
2020-04-07 13:35 ` Tejun Heo
2020-04-02 2:00 ` Qian Cai
2020-04-03 14:54 ` Tejun Heo [this message]
2020-03-25 20:20 ` 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=20200403145418.GB162390@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=cai@lca.pw \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=peterz@infradead.org \
--cc=prsood@codeaurora.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).