From: Bart Van Assche <bvanassche@acm.org>
To: Nathan Chancellor <nathan@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: linux-tip-commits@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [tip: locking/core] locking/rtmutex: Annotate API and implementation
Date: Thu, 7 May 2026 12:09:25 +0200 [thread overview]
Message-ID: <0ffcd368-d4a1-4649-a75f-881b95fd4dbe@acm.org> (raw)
In-Reply-To: <20260507084357.GA961911@ax162>
On 5/7/26 10:43 AM, Nathan Chancellor wrote:
> On Tue, May 05, 2026 at 10:55:34AM -0000, tip-bot2 for Bart Van Assche wrote:
>> The following commit has been merged into the locking/core branch of tip:
>>
>> Commit-ID: d30a456aa7ce1bab05d9b364eeacad0c9cb10cc2
>> Gitweb: https://git.kernel.org/tip/d30a456aa7ce1bab05d9b364eeacad0c9cb10cc2
>> Author: Bart Van Assche <bvanassche@acm.org>
>> AuthorDate: Tue, 05 May 2026 04:26:44 +02:00
>> Committer: Peter Zijlstra <peterz@infradead.org>
>> CommitterDate: Tue, 05 May 2026 12:50:49 +02:00
>>
>> locking/rtmutex: Annotate API and implementation
>>
>> Add lock context annotations to the rtmutex API and implementation and
>> enable lock context analysis.
>>
>> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
>> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>> Link: https://patch.msgid.link/20260505022649.870788-1-bvanassche@acm.org
>
> This breaks the build for me.
>
> $ make -skj"$(nproc)" ARCH=x86_64 LLVM=1 mrproper defconfig kernel/locking/rtmutex_api.o
> kernel/locking/rtmutex_api.c:93:1: error: expecting rt_mutex 'lock' to be held at the end of function [-Werror,-Wthread-safety-analysis]
> 93 | }
> | ^
> kernel/locking/rtmutex_api.c:90:14: note: rt_mutex acquired here
> 90 | void __sched rt_mutex_lock(struct rt_mutex *lock)
> | ^
> 1 error generated.
>
> This is with LLVM 22.1.5, in case it matters.
Hi Nathan,
I think this is the same error as what has been reported by the kernel
test robot
(https://lore.kernel.org/all/202605060005.JYWpZXr2-lkp@intel.com/).
I plan to post a new version with a fix for CONFIG_DEBUG_LOCK_ALLOC=n
soon.
Thanks,
Bart.
next prev parent reply other threads:[~2026-05-07 10:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 2:26 [PATCH v2] locking/rtmutex: Annotate API and implementation 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
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 [this message]
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=0ffcd368-d4a1-4649-a75f-881b95fd4dbe@acm.org \
--to=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=x86@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