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]
Date:   Tue, 28 Jun 2022 12:24:42 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Aaron Tomlin <atomlin@...hat.com>
Cc:     mcgrof@...nel.org, christophe.leroy@...roup.eu, cl@...ux.com,
        mbenes@...e.cz, akpm@...ux-foundation.org, jeyu@...nel.org,
        linux-kernel@...r.kernel.org, linux-modules@...r.kernel.org,
        void@...ifault.com, atomlin@...mlin.com, allen.lkml@...il.com,
        joe@...ches.com, msuchanek@...e.de, oleksandr@...alenko.name,
        jason.wessel@...driver.com, pmladek@...e.com, neelx@...hat.com,
        daniel.thompson@...aro.org, hch@...radead.org,
        Thomas Gleixner <tglx@...utronix.de>,
        linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [PATCH v11 10/14] module: kallsyms: Fix suspicious rcu usage

On Tue, 28 Jun 2022 17:21:22 +0100
Aaron Tomlin <atomlin@...hat.com> wrote:

> If I understand correctly, there is absolutely no need to explicitly
> disable preemption in this context. I will use: rcu_read_lock() and
> rcu_read_unlock(), respectively, which will then be suitable for the
> preemptible RCU implementation.

Yes, thank you very much :-)

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ