From: Bart Van Assche <bvanassche@acm.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [tip:locking/core 5/5] kernel/locking/rtmutex_api.c:93:1: warning: expecting rt_mutex 'lock' to be held at the end of function
Date: Wed, 6 May 2026 06:13:18 +0200 [thread overview]
Message-ID: <f4fce52f-5ce8-455d-bd09-148070b11ac2@acm.org> (raw)
In-Reply-To: <202605060005.JYWpZXr2-lkp@intel.com>
On 5/5/26 6:28 PM, kernel test robot wrote:
>>> kernel/locking/rtmutex_api.c:93:1: warning: expecting rt_mutex 'lock' to be held at the end of function [-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 warning generated.
The above refers to the code under "#else /* !CONFIG_DEBUG_LOCK_ALLOC
*/". I will include a fix when I repost my patch.
Thanks,
Bart.
prev parent reply other threads:[~2026-05-06 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 16:28 [tip:locking/core 5/5] kernel/locking/rtmutex_api.c:93:1: warning: expecting rt_mutex 'lock' to be held at the end of function kernel test robot
2026-05-06 4:13 ` Bart Van Assche [this message]
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=f4fce52f-5ce8-455d-bd09-148070b11ac2@acm.org \
--to=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--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