linux-kernel - Re: cpu stopper threads and load balancing leads to deadlock

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: <20180503175456.GI12217@hirez.programming.kicks-ass.net>
Date:   Thu, 3 May 2018 19:54:56 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:     Mike Galbraith <efault@....de>,
        Matt Fleming <matt@...eblueprint.co.uk>,
        Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
        Michal Hocko <mhocko@...e.com>
Subject: Re: cpu stopper threads and load balancing leads to deadlock

On Thu, May 03, 2018 at 10:18:50AM -0700, Paul E. McKenney wrote:
> > +	if (per_cpu(rcu_cpu_started, cpu))
> 
> I would log a non-splat dmesg the first time this happened, just for my
> future sanity, but otherwise looks fine.  I am a bit concerned about
> calls to rcu_cpu_starting() getting sprinkled all through the code.
> Or am I being excessively paranoid?

Don't think so, but lets first see if this at all works. If not we'll
need to figure out something else anyway.