From: Christoph Hellwig <hch@lst.de>
To: Hengyu Liang <hengyul@cs.unc.edu>
Cc: Carlos Maiolino <cem@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] xfs: fix f_bfree underflow in statfs()
Date: Thu, 12 Nov 2026 14:44:34 +0100 [thread overview]
Message-ID: <20261112134434.GA23459@lst.de> (raw)
In-Reply-To: <20261112102018.3922571-1-hengyul@cs.unc.edu>
On Thu, Nov 12, 2026 at 05:20:18AM -0500, Hengyu Liang wrote:
> The issue can be reproduced on a new 2 GiB filesystem mounted on /mnt:
>
> for i in $(seq 3000); do head -c 65536 /dev/zero > /mnt/s$i; done
> dd if=/dev/zero of=/mnt/big bs=1M
> xfs_io -x -c 'resblks 100000000' /mnt
> for i in $(seq 1 2 3000); do rm /mnt/s$i; done
> sync
> df -h /mnt
Can you add this to xfstests?
The fix itself looks good, thanks a lot!
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-11-12 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 10:20 [PATCH] xfs: fix f_bfree underflow in statfs() Hengyu Liang
2026-11-12 13:44 ` Christoph Hellwig [this message]
2026-11-12 15:07 ` Hengyu Liang
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=20261112134434.GA23459@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hengyul@cs.unc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox