[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260121131916.GA171111@noisy.programming.kicks-ass.net>
Date: Wed, 21 Jan 2026 14:19:16 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: elver@...gle.com
Cc: linux-kernel@...r.kernel.org, bigeasy@...utronix.de, mingo@...nel.org,
tglx@...utronix.de, will@...nel.org, boqun.feng@...il.com,
longman@...hat.com, hch@....de, rostedt@...dmis.org,
bvanassche@....org, llvm@...ts.linux.dev
Subject: Re: [RFC][PATCH 4/4] futex: Convert to compiler context analysis
On Wed, Jan 21, 2026 at 12:07:08PM +0100, Peter Zijlstra wrote:
> +extern void futex_q_lock(struct futex_q *q, struct futex_hash_bucket *hb)
> + __acquires(&hb->lock)
> + __acquires(q->lock_ptr);
FWIW, this 'weirdness' is because the thing cannot tell they are the
same lock and we use both forms. It's a bit tedious but that's what it
is.
Powered by blists - more mailing lists