From: Thomas Gleixner <tglx@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Mel Gorman <mgorman@techsingularity.net>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] rtmutex: Add acquire semantics for rtmutex lock acquisition slow path
Date: Fri, 21 Apr 2023 09:29:08 +0200 [thread overview]
Message-ID: <87pm7x3d8b.ffs@tglx> (raw)
In-Reply-To: <20230419072546.gD_YO2-K@linutronix.de>
On Wed, Apr 19 2023 at 09:25, Sebastian Andrzej Siewior wrote:
> On 2023-04-18 18:25:48 [+0200], Greg KH wrote:
>> > Could this be please backported to 5.15 and earlier? It is already part
>> > of the 6.X kernels. I asked about this by the end of January and I'm
>> > kindly asking again ;)
>>
>> I thought this was only an issues when using the out-of-tree RT patches
>> with these kernels, right? Or is it relevant for 5.15.y from kernel.org
>> without anything else?
>
> The out-of-tree RT patches make extensive use of the code. Since it is
> upstream code, I assumed it should go via the official stable trees.
> Without RT, the code is limited the rt_mutex_lock() used by I2C and the
> RCU booster-mutex.
Which is a reason to route it through the upstream stable trees, no?
Thanks,
tglx
next prev parent reply other threads:[~2023-04-21 7:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 15:43 [PATCH] rtmutex: Add acquire semantics for rtmutex lock acquisition slow path Sebastian Andrzej Siewior
2023-04-18 16:25 ` Greg KH
2023-04-19 7:25 ` Sebastian Andrzej Siewior
2023-04-21 7:29 ` Thomas Gleixner [this message]
2023-04-21 12:45 ` Greg KH
2023-04-21 15:30 ` Thomas Gleixner
2023-04-21 16:09 ` Sebastian Andrzej Siewior
2023-04-21 16:33 ` Thomas Gleixner
2023-04-22 15:07 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2023-01-30 11:36 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=87pm7x3d8b.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=mgorman@techsingularity.net \
--cc=stable@vger.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 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.