linux-kernel - Re: [PATCH] nvme-pci: fix parameter order in nvme_free

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20260128142255.GA3210@lst.de>
Date: Wed, 28 Jan 2026 15:22:55 +0100
From: Christoph Hellwig <hch@....de>
To: Roger Pau Monné <roger.pau@...rix.com>
Cc: Christoph Hellwig <hch@....de>, xen-devel@...ts.xenproject.org,
	Jens Axboe <axboe@...nel.dk>, Keith Busch <kbusch@...nel.org>,
	"Martin K. Petersen" <martin.petersen@...cle.com>,
	linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Sagi Grimberg <sagi@...mberg.me>
Subject: Re: [PATCH] nvme-pci: fix parameter order in nvme_free_sgls() call

On Wed, Jan 28, 2026 at 10:10:08AM +0100, Roger Pau Monné wrote:
> > > the root device as part of a kernel update is unexpected. Sadly 6.18
> > > already contained this issue, and no-one noticed, so its impact is limited?
> > 
> > This only affects non-IOMMU paths with a non-noop dma_unmap_phys.
> > So it is a very common setup, but very severe for those.  Because of
> 
> Do you mean a "not very common setup"?  Otherwise I can't parse the
> sentence.

Yes, sorry.