From: Christoph Hellwig <hch@infradead.org>
To: daejun7.park@samsung.com
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
Zorro Lang <zlang@kernel.org>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>, Jan Kara <jack@suse.cz>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH] ext4: test reads after a failed zeroout of an unwritten extent
Date: Thu, 8 Oct 2026 02:38:15 -0700 [thread overview]
Message-ID: <asdkh5WVi02SHuE2@infradead.org> (raw)
In-Reply-To: <20261008-ext4-zeroout-eio-test-v1-1-9bb66deaf646@samsung.com>
On Thu, Oct 08, 2026 at 04:39:33PM +0900, Daejun Park via B4 Relay wrote:
>
> Make the zeroout fail with dm-error and check that those blocks still
> read back as zeroes. The test mounts with dioread_lock and nodelalloc:
> with the default dioread_nolock, the extent stays unwritten until the
> I/O completes and is converted then, without this zeroout. generic/250
> and generic/252 do not hit it either, as they write with direct I/O
> while dm-error is loaded, which also leaves the extent unwritten.
Nothing in this looks ext4-specific, any reason why this is not a
generic test?
next prev parent reply other threads:[~2026-10-08 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 7:39 [PATCH] ext4: test reads after a failed zeroout of an unwritten extent Daejun Park via B4 Relay
2026-10-08 7:39 ` Daejun Park
2026-10-08 7:47 ` sashiko-bot
2026-10-08 9:38 ` Christoph Hellwig [this message]
2026-10-08 9:44 ` Daejun Park
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=asdkh5WVi02SHuE2@infradead.org \
--to=hch@infradead.org \
--cc=daejun7.park@samsung.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=tytso@mit.edu \
--cc=zlang@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.