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 for Android: free password hash cracker in your pocket

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

Date:   Tue, 7 Apr 2020 09:35:20 -0400
From:   Tejun Heo <tj@...nel.org>
To:     Qais Yousef <qais.yousef@....com>
Cc:     Qian Cai <cai@....pw>, 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 Tue, Apr 07, 2020 at 02:07:26PM +0100, Qais Yousef wrote:
> On 04/06/20 10:34, Tejun Heo wrote:
> > On Mon, Apr 06, 2020 at 11:55:23AM +0100, Qais Yousef wrote:
> > > What would be the right approach to get a fix in then? We have been skipping
> > > this test for a while and we'd like to enable it but this failure is a
> > > blocking issue.
> > 
> > Update the test so that it accounts for the async nature of the operation?
> 
> With a sleep() between the hp ops and the read? Isn't this a nasty hack?

Some operations are just async. Why is that inherently wrong?

> I was just trying to find out what can be done for 5.7. But based on your
> response this is sadly a dead end. For no reason I can comprehend.

Because it's creating real issues while trying to address a non-real problem.
It's dumb. Fix the non-real part.

Thanks.

-- 
tejun