From: sashiko-bot@kernel.org
To: "Daejun Park" <daejun7.park@samsung.com>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: test reads after a failed zeroout of an unwritten extent
Date: Thu, 08 Oct 2026 07:47:02 +0000 [thread overview]
Message-ID: <sashiko-outbox-163781@kernel.org> (raw)
In-Reply-To: <20261008-ext4-zeroout-eio-test-v1-1-9bb66deaf646@samsung.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] fs/ext4: Script submitted to wrong repository (fstests vs kernel)
- [Medium] ext4/xfstests: Typo in _require_scratch_ext4_feature_enabled function call
--
commit 15df6b5040afb28bc9e8fcc362919219d21014ba
Author: Daejun Park <daejun7.park@samsung.com>
ext4: test reads after a failed zeroout of an unwritten extent
This commit adds a new test script to verify that reading blocks from an
unwritten extent returns zeroes after a failed zeroout operation. It uses
dm-error to simulate the failure and ensures ext4 doesn't cache the unzeroed
blocks.
Link: https://lore.kernel.org/r/20261008-ext4-fc-zeroout-v2-1-55cab1e24fa3@samsung.com
> diff --git a/tests/ext4/309 b/tests/ext4/309
> new file mode 100755
> index 0000000000000..1fafd58263577
> --- /dev/null
> +++ b/tests/ext4/309
> @@ -0,0 +1,87 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2026 Samsung Electronics Co., Ltd. All Rights Reserved.
> +#
> +# FS QA Test No. 309
[ ... ]
> +. ./common/preamble
> +_begin_fstest auto quick rw prealloc eio
[Severity: Medium]
Does this script belong in the fstests repository instead of the Linux kernel
tree?
The use of the common preamble and _begin_fstest demonstrates a dependency
on the xfstests framework. Applying this patch to the kernel tree will
result in a non-functional script with unresolved dependencies.
[ ... ]
> +_require_scratch
> +_require_dm_target error
> +_require_xfs_io_command "falloc"
> +_require_xfs_io_command "fiemap"
> +_require_scratch_ext4_feature_enabled "extent"
[Severity: Medium]
Is there a typo in this function call?
The function _require_scratch_ext4_feature_enabled does not appear to exist
and should likely be _require_scratch_ext4_feature. This requirement check
will fail silently (printing an error but continuing execution), potentially
causing the test to run on unsupported configurations.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261008-ext4-zeroout-eio-test-v1-1-9bb66deaf646@samsung.com?part=1
next prev parent reply other threads:[~2026-10-08 7:47 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 [this message]
2026-10-08 9:38 ` Christoph Hellwig
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=sashiko-outbox-163781@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tytso@mit.edu \
/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.