From: Rolf Eike Beer <eb@emlix.com>
To: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org, stable@kernel.org
Subject: Backporting of 3659fb5ac29a5e6102bebe494ac789fd47fb78f4 to 5.4?
Date: Tue, 30 Sep 2025 10:34:35 +0200 [thread overview]
Message-ID: <5015244.GXAFRqVoOG@devpool92.emlix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
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?
Regards,
Eike
--
Rolf Eike Beer
emlix GmbH
Headquarters: Berliner Str. 12, 37073 Göttingen, Germany
Phone +49 (0)551 30664-0, e-mail info@emlix.com
District Court of Göttingen, Registry Number HR B 3160
Managing Directors: Heike Jordan, Dr. Uwe Kracke
VAT ID No. DE 205 198 055
Office Berlin: Panoramastr. 1, 10178 Berlin, Germany
Office Bonn: Bachstr. 6, 53115 Bonn, Germany
http://www.emlix.com
emlix - your embedded Linux partner
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 350 bytes --]
next reply other threads:[~2025-09-30 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 8:34 Rolf Eike Beer [this message]
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 ` Backporting of 3659fb5ac29a5e6102bebe494ac789fd47fb78f4 to 5.4? Keith Busch
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=5015244.GXAFRqVoOG@devpool92.emlix.com \
--to=eb@emlix.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--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 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.