From: Tal Zussman <tz2294@columbia.edu>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>, Tal Zussman <tz2294@columbia.edu>
Subject: [PATCH blktests 0/3] blktests: tests for the direct I/O fallback, splice, and bio trimming fixes
Date: Wed, 09 Sep 2026 15:39:27 -0400 [thread overview]
Message-ID: <20260909-blkdev-fixes-tests-v1-0-1f8af8665d16@columbia.edu> (raw)
Three regression tests for block device fixes under review [1],
following block/048 for the first patch of that series.
block/049 races partial O_DIRECT writes, which finish through the
direct I/O write fallback, against BLKBSZSET. block/050 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/051 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.
[1] https://lore.kernel.org/linux-block/20260828-blkdev-fixes-v2-0-32f3f40cebed@columbia.edu/
---
Tal Zussman (3):
block/049: add a direct I/O write fallback race test for block devices
block/050: add a splice read race test for block devices
block/051: add a pinned page leak test for trimmed direct writes
src/.gitignore | 3 +
src/Makefile | 9 +-
src/bio-trim-pin-leak.c | 191 ++++++++++++++++++++++++++++++++++++++++
src/dio-fallback-race.c | 229 ++++++++++++++++++++++++++++++++++++++++++++++++
src/splice-race.c | 171 ++++++++++++++++++++++++++++++++++++
tests/block/049 | 57 ++++++++++++
tests/block/049.out | 2 +
tests/block/050 | 54 ++++++++++++
tests/block/050.out | 2 +
tests/block/051 | 64 ++++++++++++++
tests/block/051.out | 2 +
11 files changed, 783 insertions(+), 1 deletion(-)
---
base-commit: 94aea0684058ffcc91e6de9c2fc85fedf1342a39
change-id: 20260909-blkdev-fixes-tests-670f566f5f85
Best regards,
--
Tal Zussman <tz2294@columbia.edu>
next reply other threads:[~2026-09-09 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 19:39 Tal Zussman [this message]
2026-09-09 19:39 ` [PATCH blktests 1/3] block/049: add a direct I/O write fallback race test for block devices Tal Zussman
2026-09-09 19:39 ` [PATCH blktests 2/3] block/050: add a splice read " Tal Zussman
2026-09-09 19:39 ` [PATCH blktests 3/3] block/051: add a pinned page leak test for trimmed direct writes Tal Zussman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260909-blkdev-fixes-tests-v1-0-1f8af8665d16@columbia.edu \
--to=tz2294@columbia.edu \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox