From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Roger Pau Monne <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org, Jens Axboe <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
stable@vger.kernel.org
Subject: Re: [PATCH] nvme-pci: fix parameter order in nvme_free_sgls() call
Date: Tue, 14 Jul 2026 13:36:55 +0200 [thread overview]
Message-ID: <alYfV2l-7p4Y3eX-@mail-itl> (raw)
In-Reply-To: <aXokOX20HMD0E_PM@kbusch-mbp>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Wed, Jan 28, 2026 at 07:59:05AM -0700, Keith Busch wrote:
> On Tue, Jan 27, 2026 at 08:59:06PM +0100, Roger Pau Monne wrote:
> > The call to nvme_free_sgls() in nvme_unmap_data() has the sg_list and sge
> > parameters swapped. This wasn't noticed by the compiler because both share
> > the same type. On a Xen PV hardware domain, and possibly any other
> > architectures that takes that path, this leads to corruption of the NVMe
> > contents.
On Wed, Jan 28, 2026 at 09:49:58AM +0100, Christoph Hellwig wrote:
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> but maybe we can reword the subject to sound less harmless, e.g.:
>
> nvme-pci: DMA unmap the correct regions in nvme_free_sgls
On Wed, Jan 28, 2026 at 07:59:05AM -0700, Keith Busch wrote:
> Thanks, applied to nvme-6.19 with updated subject.
Hi,
I think this wants to be included in v6.18 too, as it also has the
faulty commit. And indeed, I do hit this issue when running 6.18.38.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-07-14 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 19:59 [PATCH] nvme-pci: fix parameter order in nvme_free_sgls() call Roger Pau Monne
2026-01-28 8:49 ` Christoph Hellwig
2026-01-28 9:10 ` Roger Pau Monné
2026-01-28 14:22 ` Christoph Hellwig
2026-01-28 14:59 ` Keith Busch
2026-07-14 11:36 ` Marek Marczykowski-Górecki [this message]
2026-07-17 1:37 ` Sasha Levin
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=alYfV2l-7p4Y3eX-@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=roger.pau@citrix.com \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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