linux-kernel - Re: [PATCH v2 5/5] block: use chunk_sectors when evaluating stacked atomic write limits

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: <yq1tt4bt9y5.fsf@ca-mkp.ca.oracle.com>
Date: Thu, 19 Jun 2025 22:40:52 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: John Garry <john.g.garry@...cle.com>
Cc: <agk@...hat.com>, <snitzer@...nel.org>, <mpatocka@...hat.com>,
        <song@...nel.org>, <yukuai3@...wei.com>, <hch@....de>,
        <nilay@...ux.ibm.com>, <axboe@...nel.dk>, <dm-devel@...ts.linux.dev>,
        <linux-kernel@...r.kernel.org>, <linux-raid@...r.kernel.org>,
        <linux-block@...r.kernel.org>, <ojaswin@...ux.ibm.com>,
        <martin.petersen@...cle.com>
Subject: Re: [PATCH v2 5/5] block: use chunk_sectors when evaluating stacked
 atomic write limits


John,

> Furthermore, io_min may be mutated when stacking devices, and this
> makes it a poor candidate to hold the stripe size. Such an example (of
> when io_min may change) would be when the io_min is less than the
> physical block size.

io_min is not allowed to be smaller than the physical_block_size. How
did we end up violating that requirement?

  logical_block_size <= physical_block_size <= io_min <= io_opt

-- 
Martin K. Petersen