linux-kernel - Re: [PATCH] nvme: fix write_stream

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] [day] [month] [year] [list]

Message-Id: <174656083001.1636559.2161433067551641939.b4-ty@kernel.dk>
Date: Tue, 06 May 2025 13:47:10 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Kanchan Joshi <joshi.k@...sung.com>, Keith Busch <kbusch@...nel.org>, 
 Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>, 
 Caleb Sander Mateos <csander@...estorage.com>
Cc: linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvme: fix write_stream_granularity initialization


On Tue, 06 May 2025 11:54:12 -0600, Caleb Sander Mateos wrote:
> write_stream_granularity is set to max(info->runs, U32_MAX), which means
> that any RUNS value less than 2 ** 32 becomes U32_MAX, and any larger
> value is silently truncated to an unsigned int.
> 
> Use min() instead to provide the correct semantics, capping RUNS values
> at U32_MAX.
> 
> [...]

Applied, thanks!

[1/1] nvme: fix write_stream_granularity initialization
      commit: 86b6e0bd1a69efd0ed408997e0adfb85df96a0c7

Best regards,
-- 
Jens Axboe