linux-kernel - Re: [PATCH 1/2] nvme-pci: Use size_t for length fields to handle larger sizes

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: <b389f836-d88a-4b50-a2d5-dbe0ca025cb7@nvidia.com>
Date: Sat, 15 Nov 2025 22:25:00 +0000
From: Chaitanya Kulkarni <chaitanyak@...dia.com>
To: Leon Romanovsky <leon@...nel.org>, Jens Axboe <axboe@...nel.dk>, Keith
 Busch <kbusch@...nel.org>, Christoph Hellwig <hch@....de>, Sagi Grimberg
	<sagi@...mberg.me>
CC: "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>
Subject: Re: [PATCH 1/2] nvme-pci: Use size_t for length fields to handle
 larger sizes

On 11/15/25 08:22, Leon Romanovsky wrote:
> From: Leon Romanovsky<leonro@...dia.com>
>
> This patch changes the length variables from unsigned int to size_t.
> Using size_t ensures that we can handle larger sizes, as size_t is
> always equal to or larger than the previously used u32 type.
>
> Originally, u32 was used because blk-mq-dma code evolved from
> scatter-gather implementation, which uses unsigned int to describe length.
> This change will also allow us to reuse the existing struct phys_vec in places
> that don't need scatter-gather.
>
> Signed-off-by: Leon Romanovsky<leonro@...dia.com>

Looks good.

Reviewed-by: Chaitanya Kulkarni <kch@...dia.com>

-ck