linux-kernel - Re: [PATCH tip/locking/core] compiler-context-analysis: Support immediate acquisition after initialization

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: <20260115213311.GG830755@noisy.programming.kicks-ass.net>
Date: Thu, 15 Jan 2026 22:33:11 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Marco Elver <elver@...gle.com>
Cc: Ingo Molnar <mingo@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
	Will Deacon <will@...nel.org>, Boqun Feng <boqun.feng@...il.com>,
	Waiman Long <longman@...hat.com>, linux-kernel@...r.kernel.org,
	llvm@...ts.linux.dev, Bart Van Assche <bvanassche@....org>
Subject: Re: [PATCH tip/locking/core] compiler-context-analysis: Support
 immediate acquisition after initialization

On Thu, Jan 15, 2026 at 01:51:25AM +0100, Marco Elver wrote:

> Longer-term, Peter suggested to create scoped init-guards [1], which
> will both fix the issue in a more robust way and also denote clearly
> where initialization starts and ends. However, that requires new APIs,
> and won't help bridge the gap for code that just wants to opt into the
> analysis with as little other changes as possible (as suggested in [2]).

OTOH, switching to that *now*, while we have minimal files with
CONTEXT_ANALYSIS enabled, is the easiest it will ever get.

The more files get enabled, the harder it gets to switch, no?