From: Brian Foster <bfoster@redhat.com>
To: Zheng Bin <zhengbin13@huawei.com>
Cc: dchinner@redhat.com, sandeen@sandeen.net,
darrick.wong@oracle.com, linux-xfs@vger.kernel.org,
yi.zhang@huawei.com
Subject: Re: [PATCH] xfs: ensure f_bfree returned by statfs() is non-negative
Date: Tue, 12 May 2020 07:54:59 -0400 [thread overview]
Message-ID: <20200512115459.GA36658@bfoster> (raw)
In-Reply-To: <20200511024524.132384-1-zhengbin13@huawei.com>
On Mon, May 11, 2020 at 10:45:24AM +0800, Zheng Bin wrote:
> Construct an img like this:
>
> dd if=/dev/zero of=xfs.img bs=1M count=20
> mkfs.xfs -d agcount=1 xfs.img
> xfs_db -x xfs.img
> sb 0
> write fdblocks 0
> agf 0
> write freeblks 0
> write longest 0
> quit
>
> mount it, df -h /mnt(xfs mount point), will show this:
> Filesystem Size Used Avail Use% Mounted on
> /dev/loop0 17M -64Z -32K 100% /mnt
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Zheng Bin <zhengbin13@huawei.com>
> ---
Seems reasonable to me:
Reviewed-by: Brian Foster <bfoster@redhat.com>
> fs/xfs/xfs_super.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
> index e80bd2c4c279..aae469f73efe 100644
> --- a/fs/xfs/xfs_super.c
> +++ b/fs/xfs/xfs_super.c
> @@ -807,7 +807,8 @@ xfs_fs_statfs(
> statp->f_blocks = sbp->sb_dblocks - lsize;
> spin_unlock(&mp->m_sb_lock);
>
> - statp->f_bfree = fdblocks - mp->m_alloc_set_aside;
> + /* make sure statp->f_bfree does not underflow */
> + statp->f_bfree = max_t(int64_t, fdblocks - mp->m_alloc_set_aside, 0);
> statp->f_bavail = statp->f_bfree;
>
> fakeinos = XFS_FSB_TO_INO(mp, statp->f_bfree);
> --
> 2.26.0.106.g9fadedd
>
prev parent reply other threads:[~2020-05-12 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 2:45 [PATCH] xfs: ensure f_bfree returned by statfs() is non-negative Zheng Bin
2020-05-12 11:54 ` Brian Foster [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=20200512115459.GA36658@bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=yi.zhang@huawei.com \
--cc=zhengbin13@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;
as well as URLs for NNTP newsgroup(s).