From: Anand Jain <anand.jain@oracle.com>
To: Boris Burkov <boris@bur.io>,
kernel-team@fb.com, linux-btrfs@vger.kernel.org,
fstests@vger.kernel.org
Subject: Re: [PATCH] btrfs: add test for subvolid reuse with squota
Date: Sat, 13 Jul 2024 00:15:30 +0800 [thread overview]
Message-ID: <4c8a46f9-e104-44d9-9687-42429b9ac969@oracle.com> (raw)
In-Reply-To: <53cdc0c4696655a0e7a5eb62612a7b87ff4d48cd.1720547422.git.boris@bur.io>
On 10/07/2024 01:51, Boris Burkov wrote:
> Squotas are likely to leave qgroups that outlive deleted subvolids.
> Before the kernel patch
> 2b8aa78cf127 ("btrfs: qgroup: fix qgroup id collision across mounts")
> this would lead to a repeated subvolid which would collide on an
> existing qgroup id and error out with EEXIST. In snapshot creation, this
> would lead to a read only fs.
>
> Add a test which exercises the path that could create duplicate
> subvolids but with squotas enabled, which should avoid the trap.
>
> Signed-off-by: Boris Burkov <boris@bur.io>
Reviewed-by: Anand Jain <anand.jain@oracle.com>
Applied.
Thanks, Anand
> ---
> tests/btrfs/331 | 45 +++++++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/331.out | 2 ++
> 2 files changed, 47 insertions(+)
> create mode 100755 tests/btrfs/331
> create mode 100644 tests/btrfs/331.out
>
> diff --git a/tests/btrfs/331 b/tests/btrfs/331
> new file mode 100755
> index 000000000..8a99d5527
> --- /dev/null
> +++ b/tests/btrfs/331
> @@ -0,0 +1,45 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2024 Meta Platforms, Inc. All Rights Reserved.
> +#
> +# FS QA Test 331
> +#
> +# Test that btrfs does not recycle subvolume ids across remounts in a way that
> +# breaks squotas.
> +#
> +. ./common/preamble
> +_begin_fstest auto quick qgroup snapshot
> +
> +_fixed_by_kernel_commit 2b8aa78cf127 \
> + "btrfs: qgroup: fix qgroup id collision across mounts"
> +
> +. ./common/btrfs
> +_supported_fs btrfs
> +_require_scratch_enable_simple_quota
> +
> +_scratch_mkfs >> $seqres.full
> +_scratch_mount
> +$BTRFS_UTIL_PROG quota enable --simple $SCRATCH_MNT
> +
> +# Create a gap in the subvolume IDs
> +sv=$SCRATCH_MNT/sv
> +for i in $(seq 100); do
> + $BTRFS_UTIL_PROG subvolume create $sv.$i >> $seqres.full
> +done
> +for i in $(seq 50 100); do
> + $BTRFS_UTIL_PROG subvolume delete $sv.$i >> $seqres.full
> +done
> +
> +# Cycle mount triggers reading the tree_root's free objectid.
> +_scratch_cycle_mount
> +
> +# Create snapshots that could go into the used subvolid space.
> +$BTRFS_UTIL_PROG subvolume create $sv.BOOM >> $seqres.full
> +for i in $(seq 10); do
> + $BTRFS_UTIL_PROG subvolume snapshot $sv.BOOM $sv.BOOM.$i >> $seqres.full
> +done
> +
> +# success, all done
> +echo "Silence is golden"
> +status=0
> +exit
> diff --git a/tests/btrfs/331.out b/tests/btrfs/331.out
> new file mode 100644
> index 000000000..0097e61d8
> --- /dev/null
> +++ b/tests/btrfs/331.out
> @@ -0,0 +1,2 @@
> +QA output created by 331
> +Silence is golden
prev parent reply other threads:[~2024-07-12 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 17:51 [PATCH] btrfs: add test for subvolid reuse with squota Boris Burkov
2024-07-09 18:36 ` Josef Bacik
2024-07-12 16:15 ` Anand Jain [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=4c8a46f9-e104-44d9-9687-42429b9ac969@oracle.com \
--to=anand.jain@oracle.com \
--cc=boris@bur.io \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.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