Re: [PATCH blktests v3 0/4] blktests: tests for the direct I/O fallback, splice, bio trimming, and atomic write fixes

[Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>]

On Oct 15, 2026 / 12:29, Tal Zussman wrote:
> Four regression tests for block device fixes under review [1],
> following block/048 for the first patch of that series.
> 
> block/050 races partial O_DIRECT writes, which finish through the
> direct I/O write fallback, against BLKBSZSET. block/051 does the same
> with splice(). Both need CONFIG_DEBUG_VM to report the folio order
> mismatch, and skip on kernels without a 64K block size or with 64K
> pages.
> 
> block/052 issues trimmed O_DIRECT writes from a hugetlb mapping to a
> device with a 64K logical block size and checks that no huge pages
> leak, covering both the dropped and the shrunk bvec.
> 
> block/053 issues a RWF_ATOMIC write from a buffer whose last page
> cannot be pinned to a scsi_debug device with atomic_wr=1 and checks
> that the device holds all of the new data or none of it.
> 
> [1] https://lore.kernel.org/linux-block/20261009-blkdev-fixes-v6-0-307939c387df@columbia.edu/

Tal, thanks for the patches. I applied the first three patches. I left the
last patch to wait for your response to John's comments.

Of note is that block/050 and block/052 fail or hang with the current
block/for-next branch or Linus master branch. Another kernel side fix [*]
is required to make them pass.

[*] https://lore.kernel.org/all/20261022062513.77372-1-mzx199711@gmail.com/