linux-kernel - Re: [RFC][PATCH v3 6/6] rcu/tree: Use irq_work_queue

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: <20201028145428.GE2628@hirez.programming.kicks-ass.net>
Date:   Wed, 28 Oct 2020 15:54:28 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     mingo@...nel.org
Cc:     linux-kernel@...r.kernel.org, will@...nel.org, paulmck@...nel.org,
        hch@....de, axboe@...nel.dk, chris@...is-wilson.co.uk,
        davem@...emloft.net, kuba@...nel.org, fweisbec@...il.com,
        oleg@...hat.com, vincent.guittot@...aro.org
Subject: Re: [RFC][PATCH v3 6/6] rcu/tree: Use irq_work_queue_remote()

On Wed, Oct 28, 2020 at 12:07:13PM +0100, Peter Zijlstra wrote:
> AFAICT we only need/use irq_work_queue_on() on remote CPUs, since we
> can directly access local state.  So avoid the IRQ_WORK dependency and
> use the unconditionally available irq_work_queue_remote().
> 
> This survives a number of TREE01 runs.

OK, Paul mentioned on IRC that while it is extremely unlikely, this code
does not indeed guarantee it will not try to IPI self.

I'll try again.