Linux EXT4 FS development
 help / color / mirror / Atom feed
From: guzebing <guzebing1612@gmail.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	tytso@mit.edu, adilger.kernel@dilger.ca,
	libaokun@linux.alibaba.com, jack@suse.cz, ritesh.list@gmail.com,
	yi.zhang@huawei.com, bretznic@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH] ext4: reject delalloc to nodelalloc before applying remount options
Date: Tue, 18 Aug 2026 14:59:09 +0800	[thread overview]
Message-ID: <badd3ede-02ca-4fa8-9a51-a2f973dd97a3@gmail.com> (raw)
In-Reply-To: <an7Gj2vWVpbP584g@li-dc0c254c-257c-11b2-a85c-98b6c1322444.ibm.com>



On 8/14/26 3:41 PM, Ojaswin Mujoo wrote:
> Can you please add an xfstests for this. The test can stress this path and
> then use the _check_dmesg_for helper to detect if there were any
> i_reserved_data_blocks related warnings.
> 
> Regards,
> ojaswin

Hi Ojaswin,

Thanks for the review.

I have posted the corresponding fstests regression test here:

https://lore.kernel.org/linux-ext4/20260818064023.2309786-1-guzebing1612@gmail.com/

The test stresses buffered write/truncate operations in parallel with
the expected-failing remount,nodelalloc operation, and checks dmesg for
leaked delayed allocation reservations during unmount.

Locally, the test fails on an affected kernel with
i_reserved_data_blocks not cleared warnings, and passes with this patch
applied.

Thanks,
Guzebing

      reply	other threads:[~2026-08-18  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  3:48 [PATCH] ext4: reject delalloc to nodelalloc before applying remount options guzebing
2026-08-14  5:13 ` sashiko-bot
2026-08-14  7:41 ` Ojaswin Mujoo
2026-08-18  6:59   ` guzebing [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=badd3ede-02ca-4fa8-9a51-a2f973dd97a3@gmail.com \
    --to=guzebing1612@gmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=bretznic@gmail.com \
    --cc=jack@suse.cz \
    --cc=libaokun@linux.alibaba.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yi.zhang@huawei.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