From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Keenan Dong <keenanat2000@gmail.com>,
Yuan Tan <yuantan098@gmail.com>, Yifan Wu <yifanwucs@gmail.com>,
Juefei Pu <tomapufckgml@gmail.com>, Xin Liu <bird@lzu.edu.cn>,
Thomas Gleixner <tglx@kernel.org>,
Sid Kumar <sidkumar1@gmail.com>
Subject: Re: [PATCH 5.15.y] rtmutex: Use waiter::task instead of current in remove_waiter()
Date: Wed, 8 Jul 2026 21:04:48 -0400 [thread overview]
Message-ID: <20260708194323.agent5-0004@kernel.org> (raw)
In-Reply-To: <20260708150527.3212183-1-sidkumar1@gmail.com>
> Use waiter::task instead of current in all related operations in
> remove_waiter() to cure those problems.
>
> [ tglx: Fixup rt_mutex_adjust_prio_chain(), add a comment and amend the
> changelog ]
>
> [ sidk: Replace scoped_guard() macro with raw spinlock operations for
> 5.15]
The backport itself looks correct, but I can't take it alone: upstream
this commit has a Cc: stable follow-up fix, 40a25d59e85b3c
("locking/rtmutex: Skip remove_waiter() when waiter is not enqueued").
Could you resend this as a two-patch series: this patch plus a 5.15.y
adaptation of 40a25d59e85b3c? Also worth considering as a third patch is
74e144274af399 ("futex/requeue: Prevent NULL pointer dereference in
remove_waiter() on self-deadlock").
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-07-09 1:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 8:58 FAILED: patch "[PATCH] rtmutex: Use waiter::task instead of current in" failed to apply to 5.15-stable tree gregkh
2026-07-08 15:05 ` [PATCH 5.15.y] rtmutex: Use waiter::task instead of current in remove_waiter() Sid Kumar
2026-07-09 1:04 ` Sasha Levin [this message]
2026-07-09 1:53 ` Wu Frank
2026-07-09 6:53 ` Thomas Gleixner
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=20260708194323.agent5-0004@kernel.org \
--to=sashal@kernel.org \
--cc=bird@lzu.edu.cn \
--cc=keenanat2000@gmail.com \
--cc=sidkumar1@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=tomapufckgml@gmail.com \
--cc=yifanwucs@gmail.com \
--cc=yuantan098@gmail.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