linux-kernel - Folllowing up on LSF/MM RCU/idle discussion

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-next>] [day] [month] [year] [list]

Date:   Mon, 9 May 2022 08:56:33 -0700
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     jolsa@...hat.com
Cc:     linux-kernel@...r.kernel.org, peterz@...radead.org
Subject: Folllowing up on LSF/MM RCU/idle discussion

Hello, Jiri!

It was good chatting with you last week, and I hope that travels went
well!

Just wanted to follow up on the non-noinstr code between the call
to rcu_idle_enter() and rcu_idle_exit().  Although the most correct
approach is to never have non-noinstr code in arch_cpu_idle(), for all I
know there might well be architectures for which this is not feasible.
If so, one workaround would be to supply a flag set by each arch (or
subarch) that says that rcu_idle_enter() and rcu_idle_exit() are invoked
within arch_cpu_idle().

CCing Peter, who just might have an opinion on this.  ;-)

							Thanx, Paul