From: Bart Van Assche <bvanassche@acm.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Marco Elver <elver@google.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>, Boqun Feng <boqun@kernel.org>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Joel Granados <joel.granados@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>
Subject: Re: [PATCH v2] locking/rtmutex: Annotate API and implementation
Date: Tue, 5 May 2026 17:26:05 +0200 [thread overview]
Message-ID: <47e461ac-4fb5-45b3-b7ec-56f9a77c2c6b@acm.org> (raw)
In-Reply-To: <20260505140353.KoacwFc_@linutronix.de>
On 5/5/26 4:03 PM, Sebastian Andrzej Siewior wrote:
> I have here clang-22 and make with CONFIG_WARN_CONTEXT_ANALYSIS_ALL=n
> and CONFIG_WARN_CONTEXT_ANALYSIS=y. I don't see any warning without your
> patch during "make kernel/locking/".
That is expected.
> The change
> CONTEXT_ANALYSIS_rtmutex.o := y
>
> is not needed because rtmutex.o is not compiled on its own:
Agreed. Do you perhaps want me to repost this patch with that line left
out?
In case it would not be clear, the goal of this patch is to let the
compiler verify whether users of the rtmutex_*() API use this API
correctly.
Thanks,
Bart.
next prev parent reply other threads:[~2026-05-05 15:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 2:26 Bart Van Assche
2026-05-05 7:01 ` Sebastian Andrzej Siewior
2026-05-05 7:24 ` Bart Van Assche
2026-05-05 7:32 ` Sebastian Andrzej Siewior
2026-05-05 7:50 ` Bart Van Assche
2026-05-05 14:03 ` Sebastian Andrzej Siewior
2026-05-05 15:26 ` Bart Van Assche [this message]
2026-05-05 16:14 ` Sebastian Andrzej Siewior
2026-05-05 10:55 ` [tip: locking/core] " tip-bot2 for Bart Van Assche
2026-05-07 8:43 ` Nathan Chancellor
2026-05-07 10:09 ` Bart Van Assche
2026-05-08 12:14 ` Nathan Chancellor
2026-05-08 14:57 ` Peter Zijlstra
2026-05-08 16:18 ` Bart Van Assche
2026-05-05 16:12 ` [PATCH v2] " Sebastian Andrzej Siewior
2026-05-05 20:05 ` Bart Van Assche
2026-05-06 7:35 ` Sebastian Andrzej Siewior
2026-05-06 9:53 ` Bart Van Assche
2026-05-07 7:30 ` Sebastian Andrzej Siewior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47e461ac-4fb5-45b3-b7ec-56f9a77c2c6b@acm.org \
--to=bvanassche@acm.org \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=boqun@kernel.org \
--cc=clrkwllms@kernel.org \
--cc=elver@google.com \
--cc=joel.granados@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vbabka@kernel.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®