From: Mel Gorman <mgorman@techsingularity.net>
To: gregkh@linuxfoundation.org
Cc: jack@suse.cz, tglx@linutronix.de, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] rtmutex: Add acquire semantics for rtmutex lock acquisition" failed to apply to 5.15-stable tree
Date: Tue, 3 Jan 2023 09:39:37 +0000 [thread overview]
Message-ID: <20230103093937.enoobqqkdoumdmcc@techsingularity.net> (raw)
In-Reply-To: <167265568418742@kroah.com>
On Mon, Jan 02, 2023 at 11:34:44AM +0100, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 5.15-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
>
> Possible dependencies:
>
> 1c0908d8e441 ("rtmutex: Add acquire semantics for rtmutex lock acquisition slow path")
> ee042be16cb4 ("locking: Apply contention tracepoints in the slow path")
> d257cc8cb8d5 ("locking/rwsem: Make handoff bit handling more consistent")
> 7cdacc5f52d6 ("locking/rwsem: Disable preemption for spinning region")
>
> thanks,
>
> greg k-h
>
Hi Greg,
I don't plan to backport this to -stable. It's PREEMPT_RT-specific so
anyone how needs it are managing their own OOT patches. The prerequisites
are not -stable material so ideally anyone backporting would be functionally
verifying their target workloads still works ok and meets deadlines. Normal
users of stable kernels are not impacted by the bug this patch fixes.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2023-01-03 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 10:34 FAILED: patch "[PATCH] rtmutex: Add acquire semantics for rtmutex lock acquisition" failed to apply to 5.15-stable tree gregkh
2023-01-03 9:39 ` Mel Gorman [this message]
2023-01-04 11:34 ` Greg KH
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=20230103093937.enoobqqkdoumdmcc@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.