linux-kernel - Re: Deadlock due to "cpuset: Make cpuset hotplug synchronous"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <6AD62381-394F-4742-816B-12DE67DE9788@lca.pw>
Date:   Wed, 1 Apr 2020 22:00:31 -0400
From:   Qian Cai <cai@....pw>
To:     Tejun Heo <tj@...nel.org>
Cc:     Prateek Sood <prsood@...eaurora.org>,
        Li Zefan <lizefan@...wei.com>, cgroups@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: Deadlock due to "cpuset: Make cpuset hotplug synchronous"



> On Mar 25, 2020, at 3:19 PM, Tejun Heo <tj@...nel.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?