From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.com>, fstests@vger.kernel.org
Cc: Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH 3/5] btrfs/330: add test to validate ro/rw subvol mounting
Date: Wed, 20 Mar 2024 17:03:54 +0530 [thread overview]
Message-ID: <f9dc2fdf-e468-4525-bb74-47d5bc30dcc0@oracle.com> (raw)
In-Reply-To: <d61b8bd818a8f9403982f532ac21586f6c96269c.1710871719.git.dsterba@suse.com>
On 3/19/24 23:42, David Sterba wrote:
> From: Josef Bacik <josef@toxicpanda.com>
>
> Btrfs has had the ability for almost a decade to allow ro and rw
> mounting of subvols. This behavior specifically
>
> mount -o subvol=foo,ro /some/dir
> mount -o subvol=bar,rw /some/other/dir
>
> This seems simple, but because of the limitations of how we did mounting
> in ye olde days we would mark the super block as RO and the mount if we
> mounted RO first. In the case above /some/dir would instantiate the
> super block as read only and the mount point. So the second mount
> command under the covers would convert the super block to RW, and then
> allow the mount to continue.
>
> The results were still consistent, /some/dir was still read only because
> the mount was marked read only, but /some/other/dir could be written to.
>
> This is a test to make sure we maintain this behavior, as I almost
> regressed this behavior while converting us to the new mount API.
>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
looks good.
Reviewed-by: Anand Jain <anand.jain@oracle.com>
Nits below.
> ---
> tests/btrfs/330 | 54 +++++++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/330.out | 6 +++++
> 2 files changed, 60 insertions(+)
> create mode 100755 tests/btrfs/330
> create mode 100644 tests/btrfs/330.out
>
> diff --git a/tests/btrfs/330 b/tests/btrfs/330
> new file mode 100755
> index 00000000000000..3ce9840e76d028
> --- /dev/null
> +++ b/tests/btrfs/330
> @@ -0,0 +1,54 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2023 Meta Platforms, Inc. All Rights Reserved.
> +#
> +# FS QA Test No. btrfs/330
> +#
> +# Test mounting one subvolume as ro and another as rw
> +#
> +. ./common/preamble
> +_begin_fstest auto quick subvol
> +
> +_cleanup()
> +{
> + rm -rf $TEST_DIR/$seq
> +}
> +
> +# Import common functions.
> +. ./common/filter
This can be deleted, as the filter.btrfs also calls the filter.
> +. ./common/filter.btrfs
> +
> +# real QA test starts here
> +_supported_fs btrfs
> +_require_scratch
> +
> +$MOUNT_PROG -V | grep -q 'fd-based-mount'
> +[ "$?" -eq 0 ] && _notrun "mount uses the new mount api"
> +
> +_scratch_mkfs > /dev/null 2>&1
_scratch_mkfs >> $seqres.full
Errors, if any, go to stdout.
Thanks, Anand
> +_scratch_mount
> +
> +# Create our subvolumes to mount
> +$BTRFS_UTIL_PROG subvolume create $SCRATCH_MNT/foo | _filter_scratch
> +$BTRFS_UTIL_PROG subvolume create $SCRATCH_MNT/bar | _filter_scratch
> +
> +_scratch_unmount
> +
> +mkdir -p $TEST_DIR/$seq/foo
> +mkdir -p $TEST_DIR/$seq/bar
> +
> +_mount -t btrfs -o subvol=foo,ro $SCRATCH_DEV $TEST_DIR/$seq/foo
> +_mount -t btrfs -o subvol=bar,rw $SCRATCH_DEV $TEST_DIR/$seq/bar
> +
> +echo "making sure foo is read only"
> +touch $TEST_DIR/$seq/foo/baz > /dev/null 2&>1
> +ls $TEST_DIR/$seq/foo
> +
> +echo "making sure bar allows writes"
> +touch $TEST_DIR/$seq/bar/qux
> +ls $TEST_DIR/$seq/bar
> +
> +$UMOUNT_PROG $TEST_DIR/$seq/foo
> +$UMOUNT_PROG $TEST_DIR/$seq/bar
> +
> +status=0 ; exit
> diff --git a/tests/btrfs/330.out b/tests/btrfs/330.out
> new file mode 100644
> index 00000000000000..4795a2ccc8cb62
> --- /dev/null
> +++ b/tests/btrfs/330.out
> @@ -0,0 +1,6 @@
> +QA output created by 330
> +Create subvolume 'SCRATCH_MNT/foo'
> +Create subvolume 'SCRATCH_MNT/bar'
> +making sure foo is read only
> +making sure bar allows writes
> +qux
next prev parent reply other threads:[~2024-03-20 11:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 18:11 [PATCH 0/5] Btrfs fstests fixups and updates David Sterba
2024-03-19 18:12 ` [PATCH 1/5] common/verity: use the correct options for btrfs-corrupt-block David Sterba
2024-03-20 9:58 ` Anand Jain
2024-03-20 15:23 ` David Sterba
2024-03-24 7:56 ` Anand Jain
2024-03-19 18:12 ` [PATCH 2/5] btrfs/131,btrfs/172,btrfs/206: add check for block-group-tree feature in btrfs David Sterba
2024-03-20 10:01 ` Anand Jain
2024-03-19 18:12 ` [PATCH 3/5] btrfs/330: add test to validate ro/rw subvol mounting David Sterba
2024-03-20 11:33 ` Anand Jain [this message]
2024-03-20 17:01 ` Filipe Manana
2024-03-21 3:51 ` Anand Jain
2024-03-19 18:12 ` [PATCH 4/5] common/rc: use proper temporary file path in _repair_test_fs() David Sterba
2024-03-20 11:35 ` Anand Jain
2024-03-19 18:12 ` [PATCH 5/5] generic/733: disable for btrfs David Sterba
2024-03-19 21:01 ` Christoph Hellwig
2024-03-19 21:10 ` Darrick J. Wong
2024-03-19 21:16 ` Christoph Hellwig
2024-03-20 15:58 ` David Sterba
2024-03-21 21:36 ` Christoph Hellwig
2024-03-21 21:52 ` Kent Overstreet
2024-03-22 15:08 ` Josef Bacik
2024-03-22 15:45 ` Darrick J. Wong
2024-03-22 18:28 ` Kent Overstreet
2024-03-20 9:49 ` [PATCH 0/5] Btrfs fstests fixups and updates Anand Jain
2024-03-20 15:26 ` David Sterba
2024-03-21 4:09 ` [PATCH] common/btrfs: set BTRFS_CORRUPT_BLOCK_OPT_<VALUE|OFFSET> Anand Jain
2024-03-21 11:13 ` Filipe Manana
2024-03-21 12:34 ` Anand Jain
2024-03-24 8:35 ` [PATCH 0/5] Btrfs fstests fixups and updates Anand Jain
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=f9dc2fdf-e468-4525-bb74-47d5bc30dcc0@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=fstests@vger.kernel.org \
--cc=josef@toxicpanda.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