linux-kernel - Re: [PATCH] nvme: map uring_cmd data even if address is 0

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Z7yIQzPhgD1Elx-H@kbusch-mbp>
Date: Mon, 24 Feb 2025 07:54:59 -0700
From: Keith Busch <kbusch@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: Xinyu Zhang <xizhang@...estorage.com>, linux-nvme@...ts.infradead.org,
	linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
	Sagi Grimberg <sagi@...mberg.me>,
	Caleb Sander Mateos <csander@...estorage.com>
Subject: Re: [PATCH] nvme: map uring_cmd data even if address is 0

On Mon, Feb 24, 2025 at 03:33:51PM +0100, Christoph Hellwig wrote:
> On Thu, Feb 20, 2025 at 04:51:01PM -0700, Xinyu Zhang wrote:
> > When using kernel registered bvec fixed buffers, the "address" is
> > actually the offset into the bvec rather than userspace address.
> > Therefore it can be 0.
> 
> How is that actually going to work?  Who is interpreting that address?

io_import_fixed() treats the address as an offset into its bio_vec.