From: Pankaj Raghav <pankaj.raghav@linux.dev>
To: Zhang Yi <yi.zhang@huaweicloud.com>
Cc: Pankaj Raghav <p.raghav@samsung.com>,
zlang@redhat.com, fstests@vger.kernel.org, djwong@kernel.org,
yi.zhang@huawei.com, linux-xfs@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] generic/795: add unaligned boundary test cases for WRITE_ZEROES
Date: Thu, 9 Jul 2026 09:55:53 +0200 [thread overview]
Message-ID: <3bec72fe-c096-4db8-b33c-50846de16f42@linux.dev> (raw)
In-Reply-To: <82e2b175-7961-4133-94f6-209f97cbafe7@huaweicloud.com>
>>
>> I had a similar question as Christoph. But I will include dirty unwritten
>> test case as well, as ext4 impl may slightly differ.
>>
>> Thanks for the point about the FIEMAP. I will change it to use filefrag.
>>
>> I will send the patches soon.
>
> Thank you!
>
>>
>> Btw, I tested ext4 and it failed the test. I assume there is a fix on the way for ext4? And did you
>> also test this for bigalloc configuration? I ran into some issues with bigrtalloc (alloc size >
>> block size). I am wondering if you hit a similar issue in ext4 for biglloc configs.
>>
>
> Yes, there are issues in the current ext4 that need to be fixed, and I
> have already sent out the fixed patch set [1]. I have run several
> rounds of this test on my machine, including bigalloc scenarios, and
> everything looks fine by now.
>
> After applying this patch set, does the issue you encountered still
> exist?
>
I still haven't tried your patchset. I tried running this test on upstream
kernel and noticed a failure. Then when I saw the ext4 mailing list and there
were some discussion already ongoing regarding this issue.
I can give your patchset a try as well :)
--
Pankaj
prev parent reply other threads:[~2026-07-09 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 12:54 [PATCH] generic/795: add unaligned boundary test cases for WRITE_ZEROES Pankaj Raghav
2026-07-07 3:08 ` Zhang Yi
2026-07-07 5:10 ` Christoph Hellwig
2026-07-07 6:38 ` Zhang Yi
2026-07-08 13:21 ` Pankaj Raghav
2026-07-09 2:32 ` Zhang Yi
2026-07-09 7:55 ` Pankaj Raghav [this message]
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=3bec72fe-c096-4db8-b33c-50846de16f42@linux.dev \
--to=pankaj.raghav@linux.dev \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=p.raghav@samsung.com \
--cc=yi.zhang@huawei.com \
--cc=yi.zhang@huaweicloud.com \
--cc=zlang@redhat.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 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.