From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Oleg Nesterov <oleg@redhat.com>
Cc: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>, Tejun Heo <tj@kernel.org>,
David Vernet <dvernet@meta.com>, Barret Rhoden <brho@google.com>,
Josh Don <joshdon@google.com>, Crystal Wood <crwood@redhat.com>,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
Juri Lelli <juri.lelli@redhat.com>,
Ben Segall <bsegall@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@redhat.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Wander Lairson Costa <wander@redhat.com>
Subject: Re: usage of DEFINE_WAIT_OVERRIDE_MAP(LD_WAIT_SLEEP)
Date: Thu, 23 Oct 2025 15:53:16 +0200 [thread overview]
Message-ID: <20251023135316.1ZRx0UU5@linutronix.de> (raw)
In-Reply-To: <20251020145310.GA9608@redhat.com>
On 2025-10-20 16:53:10 [+0200], Oleg Nesterov wrote:
> Hi Sebastian,
Hi,
> > You are correct Oleg. I've been just verifying it and yes: LD_WAIT_SLEEP
> > suppresses also mutex while the intention is to only suppress
> > spinlock_t.
> > We have four users in tree, based on quick check all four should use
> > CONFIG, three of them do use SLEEP.
>
> No ;)
>
> I was going to send the patch which does s/SLEEP/CONFIG/, but this
> would be wrong. printk_legacy_map can use LD_WAIT_CONFIG, but lets
> look at debug_objects_fill_pool()
>
> if (!IS_ENABLED(CONFIG_PREEMPT_RT) || preemptible()) {
> /*
> * Annotate away the spinlock_t inside raw_spinlock_t warning
> * by temporarily raising the wait-type to WAIT_SLEEP, matching
> * the preemptible() condition above.
> */
> static DEFINE_WAIT_OVERRIDE_MAP(fill_pool_map, LD_WAIT_SLEEP);
> lock_map_acquire_try(&fill_pool_map);
> fill_pool();
> lock_map_release(&fill_pool_map);
> }
>
> If CONFIG_PREEMPT_RT=y and preemptible() is true, LD_WAIT_CONFIG won't work.
> lockdep will complain if fill_pool() takes a spinlock_t, spinlock is
> LD_WAIT_SLEEP on RT.
Where is this? This is then wrong then because _SLEEP is for MUTEX and
those things that sleep-sleep and pretend to sleep.
spinlock_t should be LD_WAIT_CONFIG. This is used in
include/linux/spinlock_types.h via SPIN_DEP_MAP_INIT which is only
defined once as LD_WAIT_CONFIG.
rt_mutex is defined as LD_WAIT_SLEEP but this one is not the one we use
for spinlock_t.
What you want to have working in the end is the following scenario:
|static DEFINE_SPINLOCK(lock_spinlock);
|static DEFINE_RAW_SPINLOCK(lock_raw_spinlock);
|static DEFINE_RAW_SPINLOCK(lock_raw_spinlock2);
|
|static void lockdep_test(void)
|{
| static DEFINE_WAIT_OVERRIDE_MAP(put_task_map, LD_WAIT_CONFIG);
|
| raw_spin_lock(&lock_raw_spinlock);
| lock_map_acquire_try(&put_task_map);
|
| spin_lock(&lock_spinlock);
| spin_unlock(&lock_spinlock);
|
| raw_spin_lock(&lock_raw_spinlock2);
| raw_spin_unlock(&lock_raw_spinlock2);
|
| lock_map_release(&put_task_map);
| raw_spin_unlock(&lock_raw_spinlock);
|}
This will work. On RT as well but is wrong and will not happen due to
the preemptible() check. On !RT it will so you want lockdep to be quiet.
>
> Oleg.
Sebastian
next prev parent reply other threads:[~2025-10-23 13:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 14:03 [PATCH v6] sched: do not call __put_task_struct() on rt if pi_blocked_on is set Luis Claudio R. Goncalves
2025-07-10 16:19 ` Valentin Schneider
2025-07-14 14:15 ` Sebastian Andrzej Siewior
2025-07-28 20:14 ` Oleg Nesterov
2025-07-29 7:33 ` Luis Claudio R. Goncalves
2025-07-29 11:47 ` Oleg Nesterov
2025-07-29 12:45 ` Luis Claudio R. Goncalves
2025-07-29 13:09 ` Oleg Nesterov
2025-08-01 10:24 ` Oleg Nesterov
2025-08-01 10:51 ` Luis Claudio R. Goncalves
2025-08-11 10:59 ` Sebastian Andrzej Siewior
2025-08-11 11:06 ` Oleg Nesterov
2025-08-11 12:16 ` Sebastian Andrzej Siewior
2025-08-11 12:19 ` Oleg Nesterov
2025-08-11 12:27 ` Sebastian Andrzej Siewior
2025-10-20 14:53 ` usage of DEFINE_WAIT_OVERRIDE_MAP(LD_WAIT_SLEEP) Oleg Nesterov
2025-10-23 13:53 ` Sebastian Andrzej Siewior [this message]
2025-10-23 15:29 ` Oleg Nesterov
2025-10-23 15:37 ` Sebastian Andrzej Siewior
2025-10-23 15:53 ` Oleg Nesterov
2025-10-23 19:23 ` Sebastian Andrzej Siewior
2025-10-24 10:26 ` Oleg Nesterov
2025-10-24 10:39 ` Sebastian Andrzej Siewior
2025-10-24 15:19 ` Oleg Nesterov
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=20251023135316.1ZRx0UU5@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=brho@google.com \
--cc=bsegall@google.com \
--cc=clrkwllms@kernel.org \
--cc=crwood@redhat.com \
--cc=dietmar.eggemann@arm.com \
--cc=dvernet@meta.com \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wander@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).