linux-kernel - Re: [PATCH AUTOSEL 6.14 295/642] nvme: map uring

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: <aCyOGIDzSaI4p47X@lappy>
Date: Tue, 20 May 2025 10:13:44 -0400
From: Sasha Levin <sashal@...nel.org>
To: Caleb Sander Mateos <csander@...estorage.com>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Xinyu Zhang <xizhang@...estorage.com>, Jens Axboe <axboe@...nel.dk>,
	Ming Lei <ming.lei@...hat.com>, Keith Busch <kbusch@...nel.org>,
	sagi@...mberg.me, linux-nvme@...ts.infradead.org
Subject: Re: [PATCH AUTOSEL 6.14 295/642] nvme: map uring_cmd data even if
 address is 0

On Mon, May 05, 2025 at 04:15:47PM -0700, Caleb Sander Mateos wrote:
>I wouldn't backport this change to any releases. It's a potential
>behavior change if a userspace application was submitting NVMe
>passthru commands with a NULL data pointer but nonzero data length and
>expecting the data buffer to be ignored. And supporting the data field
>set to 0 is only necessary for ublk zero-copy, which is introduced in
>6.15.

I'll drop it, thanks!

-- 
Thanks,
Sasha