From: David Sterba <dsterba@suse.cz>
To: ethanlien <ethanlien@synology.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: fix qgroup reserve overflow break the qgroup limit
Date: Mon, 7 Mar 2022 15:47:09 +0100 [thread overview]
Message-ID: <20220307144709.GH12643@twin.jikos.cz> (raw)
In-Reply-To: <20220307100004.24759-1-ethanlien@synology.com>
On Mon, Mar 07, 2022 at 06:00:04PM +0800, ethanlien wrote:
> We use extent_changeset->bytes_changed in qgroup_reserve_data() to record
> how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the
> bytes_changed is set as "unsigned int", and it will overflow if we try to
> fallocate a range larger than 4GiB. The result is we reserve less bytes
> and eventually break the qgroup limit.
>
> The following example test script reproduces the problem:
>
> $ cat qgroup-overflow.sh
> #!/bin/bash
>
> DEV=/dev/sdj
> MNT=/mnt/sdj
>
> mkfs.btrfs -f $DEV
> mount $DEV $MNT
>
> # Set qgroup limit to 2GiB.
> btrfs quota enable $MNT
> btrfs qgroup limit 2G $MNT
>
> # Try to fallocate a 3GiB file. This should fail.
> echo
> echo "Try to fallocate a 3GiB file..."
> fallocate -l 3G $MNT/3G.file
>
> # Try to fallocate a 5GiB file.
> echo
> echo "Try to fallocate a 5GiB file..."
> fallocate -l 5G $MNT/5G.file
>
> # See we break the qgroup limit.
> echo
> sync
> btrfs qgroup show -r $MNT
>
> umount $MNT
>
> When running the test:
>
> $ ./qgroup-overflow.sh
> (...)
>
> Try to fallocate a 3GiB file...
> fallocate: fallocate failed: Disk quota exceeded
>
> Try to fallocate a 5GiB file...
>
> qgroupid rfer excl max_rfer
> -------- ---- ---- --------
> 0/5 5.00GiB 5.00GiB 2.00GiB
>
> Since we have no control of how bytes_changed is used, it's better to
> set it to u64.
>
> Signed-off-by: ethanlien <ethanlien@synology.com>
Added to misc-next, thanks.
prev parent reply other threads:[~2022-03-07 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 10:00 [PATCH] btrfs: fix qgroup reserve overflow break the qgroup limit ethanlien
2022-03-07 11:08 ` Qu Wenruo
2022-03-07 14:47 ` David Sterba [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=20220307144709.GH12643@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=ethanlien@synology.com \
--cc=linux-btrfs@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