linux-kernel - Re: [PATCH v1 11/14] futex: Implement FUTEX2

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2eb23678-e1c7-816d-4807-f324c771e6ed@gentwo.org>
Date: Wed, 12 Jun 2024 10:07:44 -0700 (PDT)
From: "Christoph Lameter (Ampere)" <cl@...two.org>
To: Peter Zijlstra <peterz@...radead.org>
cc: Thomas Gleixner <tglx@...utronix.de>, axboe@...nel.dk, 
    linux-kernel@...r.kernel.org, mingo@...hat.com, dvhart@...radead.org, 
    dave@...olabs.net, andrealmeid@...lia.com, 
    Andrew Morton <akpm@...ux-foundation.org>, urezki@...il.com, 
    hch@...radead.org, lstoakes@...il.com, Arnd Bergmann <arnd@...db.de>, 
    linux-api@...r.kernel.org, linux-mm@...ck.org, linux-arch@...r.kernel.org, 
    malteskarupke@....de
Subject: Re: [PATCH v1 11/14] futex: Implement FUTEX2_NUMA

On Mon, 31 Jul 2023, Peter Zijlstra wrote:

>> Is nr_node_ids guaranteed to be stable after init? It's marked
>> __read_mostly, but not __ro_after_init.
>
> AFAICT it is only ever written to in setup_nr_node_ids() and that is all
> __init code. So I'm thinking this could/should indeed be
> __ro_after_init. Esp. so since it is an exported variable.
>
> Mike?

Its stable and lots of other components depend on it like f.e. the size of 
cpumasks.