linux-kernel - Re: [PATCH v2 rcu 0/8] NMI-safe SRCU reader API

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: <87k04x4e0r.fsf@jogness.linutronix.de>
Date:   Tue, 18 Oct 2022 12:39:40 +0206
From:   John Ogness <john.ogness@...utronix.de>
To:     paulmck@...nel.org, rcu@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, kernel-team@...com,
        rostedt@...dmis.org, tglx@...utronix.de, pmladek@...e.com,
        Frederic Weisbecker <frederic@...nel.org>
Subject: Re: [PATCH v2 rcu 0/8] NMI-safe SRCU reader API

Hi Paul,

On 2022-09-29, "Paul E. McKenney" <paulmck@...nel.org> wrote:
> This RFC series provides the second version of an NMI-safe SRCU reader
> API in the guise of srcu_read_lock_nmisafe() and
> srcu_read_unlock_nmisafe().

I would like to post a new series for printk that will rely on the
NMI-safe reader API. From the feedback of this series it appears that
the RFC v2 is an acceptable starting point. How should we proceed?

Will Frederic be sending a patch for the extra safety checks using
srcu_nmi_flags? Are you planning on posting a new version? Should I
include this or another version within my upcoming series?

Thanks for all your help on this!

John