From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v9 9/9] btrfs: Use sb_want_write() to protect sysfs feature change.
Date: Fri, 15 May 2015 14:47:37 +0800 [thread overview]
Message-ID: <55559689.4090305@cn.fujitsu.com> (raw)
In-Reply-To: <1424048525-26274-1-git-send-email-quwenruo@cn.fujitsu.com>
Ping.
Any comments?
Other v7 patchset is reviewed by David.
But I didn't find it in 4.1 merge windows.
Is something wrong or we are waiting for the vfs patch merged first?
Thanks,
Qu
-------- Original Message --------
Subject: [PATCH v9 9/9] btrfs: Use sb_want_write() to protect sysfs
feature change.
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Date: 2015年02月16日 09:02
> Just like label change, use sb_want_write() to do a correct protection.
>
> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
> ---
> v4:
> Newly introduced.
> v5:
> Change to sb_want_write().
> v6:
> Move sb_want_write() to the beginning of the function.
> v7:
> None
> v8:
> Move sb_want_write() after get fs_info.
> v9:
> Fix a unpaired sb_drop_write() in error handler.
> ---
> fs/btrfs/sysfs.c | 25 +++++++++++++++++--------
> 1 file changed, 17 insertions(+), 8 deletions(-)
>
> diff --git a/fs/btrfs/sysfs.c b/fs/btrfs/sysfs.c
> index 7e548f7..19876ba 100644
> --- a/fs/btrfs/sysfs.c
> +++ b/fs/btrfs/sysfs.c
> @@ -121,10 +121,14 @@ static ssize_t btrfs_feature_attr_store(struct kobject *kobj,
> if (!fs_info)
> return -EPERM;
>
> - ret = kstrtoul(skip_spaces(buf), 0, &val);
> + ret = sb_want_write(fs_info->sb);
> if (ret)
> return ret;
>
> + ret = kstrtoul(skip_spaces(buf), 0, &val);
> + if (ret)
> + goto out;
> +
> if (fa->feature_set == FEAT_COMPAT) {
> set = BTRFS_FEATURE_COMPAT_SAFE_SET;
> clear = BTRFS_FEATURE_COMPAT_SAFE_CLEAR;
> @@ -141,22 +145,25 @@ static ssize_t btrfs_feature_attr_store(struct kobject *kobj,
> /* Nothing to do */
> if ((val && (features & fa->feature_bit)) ||
> (!val && !(features & fa->feature_bit)))
> - return count;
> + goto out;
>
> if ((val && !(set & fa->feature_bit)) ||
> (!val && !(clear & fa->feature_bit))) {
> btrfs_info(fs_info,
> "%sabling feature %s on mounted fs is not supported.",
> val ? "En" : "Dis", fa->kobj_attr.attr.name);
> - return -EPERM;
> + ret = -EPERM;
> + goto out;
> }
>
> btrfs_info(fs_info, "%s %s feature flag",
> val ? "Setting" : "Clearing", fa->kobj_attr.attr.name);
>
> trans = btrfs_start_transaction(fs_info->fs_root, 0);
> - if (IS_ERR(trans))
> - return PTR_ERR(trans);
> + if (IS_ERR(trans)) {
> + ret = PTR_ERR(trans);
> + goto out;
> + }
>
> spin_lock(&fs_info->super_lock);
> features = get_features(fs_info, fa->feature_set);
> @@ -168,10 +175,12 @@ static ssize_t btrfs_feature_attr_store(struct kobject *kobj,
> spin_unlock(&fs_info->super_lock);
>
> ret = btrfs_commit_transaction(trans, fs_info->fs_root);
> - if (ret)
> - return ret;
>
> - return count;
> +out:
> + sb_drop_write(fs_info->sb);
> + if (!ret)
> + return count;
> + return ret;
> }
>
> static umode_t btrfs_feature_visible(struct kobject *kobj,
>
next prev parent reply other threads:[~2015-05-15 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 1:02 [PATCH v9 9/9] btrfs: Use sb_want_write() to protect sysfs feature change Qu Wenruo
2015-02-16 14:44 ` David Sterba
2015-05-15 6:47 ` Qu Wenruo [this message]
2015-06-19 5:23 ` Qu Wenruo
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=55559689.4090305@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).