public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: Josef Bacik <josef@toxicpanda.com>,
	linux-btrfs@vger.kernel.org, kernel-team@fb.com,
	linux-fsdevel@vger.kernel.org, brauner@kernel.org
Subject: Re: [PATCH v2 02/18] btrfs: split out the mount option validation code into its own helper
Date: Tue, 14 Nov 2023 18:35:41 +0100	[thread overview]
Message-ID: <20231114173541.GD11264@twin.jikos.cz> (raw)
In-Reply-To: <f6180d3c-0bbc-47e5-b098-6f1210c23be6@oracle.com>

On Tue, Nov 14, 2023 at 02:32:16PM +0800, Anand Jain wrote:
> 
> > +static bool check_options(struct btrfs_fs_info *info, unsigned long flags)
> > +{
> > +	if (!(flags & SB_RDONLY) &&
> > +	    (check_ro_option(info, BTRFS_MOUNT_NOLOGREPLAY, "nologreplay") ||
> > +	     check_ro_option(info, BTRFS_MOUNT_IGNOREBADROOTS, "ignorebadroots") ||
> > +	     check_ro_option(info, BTRFS_MOUNT_IGNOREDATACSUMS, "ignoredatacsums")))
> > +		return false;
> > +
> > +	if (btrfs_fs_compat_ro(info, FREE_SPACE_TREE) &&
> > +	    !btrfs_test_opt(info, FREE_SPACE_TREE) &&
> > +	    !btrfs_test_opt(info, CLEAR_CACHE)) {
> > +		btrfs_err(info, "cannot disable free space tree");
> > +		return false;
> > +	}
> > +	if (btrfs_fs_compat_ro(info, BLOCK_GROUP_TREE) &&
> > +	     !btrfs_test_opt(info, FREE_SPACE_TREE)) {
> > +		btrfs_err(info, "cannot disable free space tree with block-group-tree feature");
> > +		return false;
> > +	}
> > +
> > +	if (btrfs_check_mountopts_zoned(info))
> > +		return false;
> > +
> 
> 
> <snip>
> 
> > -check:
> > -	/* We're read-only, don't have to check. */
> > -	if (new_flags & SB_RDONLY)
> > -		goto out;
> > -
> > -	if (check_ro_option(info, BTRFS_MOUNT_NOLOGREPLAY, "nologreplay") ||
> > -	    check_ro_option(info, BTRFS_MOUNT_IGNOREBADROOTS, "ignorebadroots") ||
> > -	    check_ro_option(info, BTRFS_MOUNT_IGNOREDATACSUMS, "ignoredatacsums"))
> > -		ret = -EINVAL;
> >   out:
> > -	if (btrfs_fs_compat_ro(info, FREE_SPACE_TREE) &&
> > -	    !btrfs_test_opt(info, FREE_SPACE_TREE) &&
> > -	    !btrfs_test_opt(info, CLEAR_CACHE)) {
> > -		btrfs_err(info, "cannot disable free space tree");
> > +	if (!ret && !check_options(info, new_flags))
> >   		ret = -EINVAL;
> > -	}
> > -	if (btrfs_fs_compat_ro(info, BLOCK_GROUP_TREE) &&
> > -	     !btrfs_test_opt(info, FREE_SPACE_TREE)) {
> > -		btrfs_err(info, "cannot disable free space tree with block-group-tree feature");
> > -		ret = -EINVAL;
> > -	}
> > -	if (!ret)
> > -		ret = btrfs_check_mountopts_zoned(info);
> > -	if (!ret && !remounting) {
> > -		if (btrfs_test_opt(info, SPACE_CACHE))
> > -			btrfs_info(info, "disk space caching is enabled");
> > -		if (btrfs_test_opt(info, FREE_SPACE_TREE))
> > -			btrfs_info(info, "using free space tree");
> > -	}
> >   	return ret;
> >   }
> 
> 
> Before this patch, we verified all the above checks simultaneously.
> Now, for each error, we return without checking the rest.
> As a result, if there are multiple failures in the above checks,
> we report them sequentially. This is not a bug, but the optimization
> we had earlier has been traded off for cleaner code.
> IMO it is good to keep the optimization.

I would not say it's cleaner code, it's doing something else than
before. I think we should keep the behaviour 1:1 unless there's a reason
for that, the changelog does not say.

  reply	other threads:[~2023-11-14 17:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 19:08 [PATCH v2 00/18] btrfs: convert to the new mount API Josef Bacik
2023-11-08 19:08 ` [PATCH v2 01/18] fs: indicate request originates from old mount api Josef Bacik
2023-11-08 19:08 ` [PATCH v2 02/18] btrfs: split out the mount option validation code into its own helper Josef Bacik
2023-11-14  6:32   ` Anand Jain
2023-11-14 17:35     ` David Sterba [this message]
2023-11-08 19:08 ` [PATCH v2 03/18] btrfs: set default compress type at btrfs_init_fs_info time Josef Bacik
2023-11-08 19:08 ` [PATCH v2 04/18] btrfs: move space cache settings into open_ctree Josef Bacik
2023-11-15  0:06   ` Anand Jain
2023-11-20 21:54     ` Josef Bacik
2023-11-08 19:08 ` [PATCH v2 05/18] btrfs: do not allow free space tree rebuild on extent tree v2 Josef Bacik
2023-11-15  9:49   ` Anand Jain
2023-11-16 20:09     ` David Sterba
2023-11-08 19:08 ` [PATCH v2 06/18] btrfs: split out ro->rw and rw->ro helpers into their own functions Josef Bacik
2023-11-08 19:08 ` [PATCH v2 07/18] btrfs: add a NOSPACECACHE mount option flag Josef Bacik
2023-11-08 19:08 ` [PATCH v2 08/18] btrfs: add fs_parameter definitions Josef Bacik
2023-11-14 17:49   ` David Sterba
2023-11-08 19:08 ` [PATCH v2 09/18] btrfs: add parse_param callback for the new mount api Josef Bacik
2023-11-14 18:13   ` David Sterba
2023-11-22 16:12     ` Josef Bacik
2023-11-08 19:08 ` [PATCH v2 10/18] btrfs: add fs context handling functions Josef Bacik
2023-11-08 19:08 ` [PATCH v2 11/18] btrfs: add reconfigure callback for fs_context Josef Bacik
2023-11-14 18:23   ` David Sterba
2023-11-08 19:08 ` [PATCH v2 12/18] btrfs: add get_tree callback for new mount API Josef Bacik
2023-11-14 18:35   ` David Sterba
2023-11-08 19:08 ` [PATCH v2 13/18] btrfs: handle the ro->rw transition for mounting different subovls Josef Bacik
2023-11-08 19:08 ` [PATCH v2 14/18] btrfs: switch to the new mount API Josef Bacik
2023-11-08 19:08 ` [PATCH v2 15/18] btrfs: move the device specific mount options to super.c Josef Bacik
2023-11-08 19:08 ` [PATCH v2 16/18] btrfs: remove old mount API code Josef Bacik
2023-11-08 19:08 ` [PATCH v2 17/18] btrfs: move one shot mount option clearing to super.c Josef Bacik
2023-11-08 19:08 ` [PATCH v2 18/18] btrfs: set clear_cache if we use usebackuproot Josef Bacik
2023-11-08 23:02 ` [PATCH v2 00/18] btrfs: convert to the new mount API Neal Gompa
2023-11-09 11:55 ` Johannes Thumshirn
2023-11-09 12:55 ` Christian Brauner

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=20231114173541.GD11264@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=anand.jain@oracle.com \
    --cc=brauner@kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@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