From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Kevin Brandstatter <icarusthecow@gmail.com>,
Wang Shilong <wangshilong1991@gmail.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs_qgroup_create unused parameter
Date: Fri, 25 Jul 2014 09:17:21 +0800 [thread overview]
Message-ID: <53D1B021.6040501@cn.fujitsu.com> (raw)
In-Reply-To: <53D1958D.1070202@gmail.com>
Hi Kevin,
On 07/25/2014 07:23 AM, Kevin Brandstatter wrote:
> I submitted a patch for this a week or two ago
> (https://patchwork.kernel.org/patch/4486121/), but latest for-linus
> doesn't have it merged, is it just being put of as minor, or is there a
> problem with it?
I believe your patch will be picked up by Chris and sent to Linus
when next merge window is open.
Since Chris is sometimes busy, patch merging is always
delayed for some time.
Thanks,
Wang
>
> -Kevin
>
> On 07/04/2014 09:09 PM, Wang Shilong wrote:
>> Hi
>>
>> I think you are right, @name here is unneeded..
>> You can give a patch for that.^_^
>>
>> Wang
>>> |The code is pasted below for convenience of reference, but in the function to
>>> create a qgruop, it taks a 4th parameter (char * name). I assume this is the name
>>> of the path to limit, however, i don't see where its used anywhere in the function.
>>>
>>> -Kevin Brandstatter
>>>
>>> int btrfs_create_qgroup(struct btrfs_trans_handle *trans,
>>> struct btrfs_fs_info *fs_info, u64 qgroupid, *char** *****name**)*
>>> {
>>> struct btrfs_root *quota_root;
>>> struct btrfs_qgroup *qgroup;
>>> int ret = 0;
>>>
>>> mutex_lock(&fs_info->qgroup_ioctl_lock);
>>> quota_root = fs_info->quota_root;
>>> if (!quota_root) {
>>> ret = -EINVAL;
>>> goto out;
>>> }
>>> qgroup = find_qgroup_rb(fs_info, qgroupid);
>>> if (qgroup) {
>>> ret = -EEXIST;
>>> goto out;
>>> }
>>>
>>> ret = add_qgroup_item(trans, quota_root, qgroupid);
>>> if (ret)
>>> goto out;
>>>
>>> spin_lock(&fs_info->qgroup_lock);
>>> qgroup = add_qgroup_rb(fs_info, qgroupid);
>>> spin_unlock(&fs_info->qgroup_lock);
>>>
>>> if (IS_ERR(qgroup))
>>> ret = PTR_ERR(qgroup);
>>> out:
>>> mutex_unlock(&fs_info->qgroup_ioctl_lock);
>>> return ret;
>>> }|
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-07-25 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 20:04 btrfs_qgroup_create unused parameter Kevin Brandstatter
2014-07-05 2:09 ` Wang Shilong
2014-07-24 23:23 ` Kevin Brandstatter
2014-07-25 1:17 ` Wang Shilong [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=53D1B021.6040501@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=icarusthecow@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangshilong1991@gmail.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;
as well as URLs for NNTP newsgroup(s).