From: Keith Busch <kbusch@kernel.org>
To: Rolf Eike Beer <eb@emlix.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, stable@kernel.org
Subject: Re: Backporting of 3659fb5ac29a5e6102bebe494ac789fd47fb78f4 to 5.4?
Date: Tue, 30 Sep 2025 14:34:30 +0200 [thread overview]
Message-ID: <aNvOVkpKhEHXAxcF@kbusch-mbp> (raw)
In-Reply-To: <5015244.GXAFRqVoOG@devpool92.emlix.com>
On Tue, Sep 30, 2025 at 10:34:35AM +0200, Rolf Eike Beer wrote:
> Hi all,
>
> I just noticed that 3659fb5ac29a5e6102bebe494ac789fd47fb78f4 ("nvme: fix
> multipath crash caused by flush request when blktrace is enabled") has not been
> backported into 5.4 stable kernels, leaving CVE-2022-50388 unfixed. I assume
> this has happened because it did not trivially apply.
>
> Is this assumption correct? In this case please see the patch I'll send as
> reply. If not, what is the reason?
It doesn't apply, though it's a trivial conflict resolution.
prev parent reply other threads:[~2025-09-30 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 8:34 Backporting of 3659fb5ac29a5e6102bebe494ac789fd47fb78f4 to 5.4? Rolf Eike Beer
2025-09-30 8:43 ` [PATCH 5.4] nvme: fix multipath crash caused by flush request when blktrace is enabled Rolf Eike Beer
2025-09-30 12:34 ` Keith Busch [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=aNvOVkpKhEHXAxcF@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=eb@emlix.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=stable@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