From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V2 RESEND] btrfs: pass the error code to the btrfs_std_error and log ret
Date: Mon, 2 May 2016 07:06:29 +0800 [thread overview]
Message-ID: <57268BF5.7010408@oracle.com> (raw)
In-Reply-To: <20160316131019.GM21722@twin.jikos.cz>
On 03/16/2016 09:10 PM, David Sterba wrote:
> On Thu, Mar 10, 2016 at 12:22:15PM +0800, Anand Jain wrote:
>> This patch will log return value of add/del_qgroup_relation() and pass the
>> err code of btrfs_run_qgroups to the btrfs_std_error().
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> v2: fix the forgotten git commit amend, to take in compile fail, sorry
>>
>> fs/btrfs/ioctl.c | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
>> index f704d1c..f43a104 100644
>> --- a/fs/btrfs/ioctl.c
>> +++ b/fs/btrfs/ioctl.c
>> @@ -4803,10 +4803,15 @@ static long btrfs_ioctl_qgroup_assign(struct file *file, void __user *arg)
>> sa->src, sa->dst);
>> }
>>
>> + if (ret)
>> + btrfs_err(root->fs_info,
>> + "add/del qgroup relation failed, assign %llu ret %d",
>> + sa->assign, ret);
>
> It's just logging an error, but it should really fail, without a
> message. The error code will tell what went wrong. Assigning existing
> qgroups is eg. EEXIST, if either doesn't exist then ENOENT. There's a
> FIXME a few lines above that should be addressed.
>
> I'd like to avoid the message in this case because it should be handled
> by the ioctl caller, otherwise it could be just flooding the system log.
>
>> +
>> /* update qgroup status and info */
>> err = btrfs_run_qgroups(trans, root->fs_info);
>> if (err < 0)
>> - btrfs_std_error(root->fs_info, ret,
>> + btrfs_std_error(root->fs_info, err,
This patch is missing in the 'dev-del-by-id' branch. I agree with your
the above comments, however the key intention of this patch was to get
the correct parameter passed to the btrfs_std_error(). And the above
btrfs_err() log should still help/motivate to get the part you
mentioned corrected.
Thanks, -Anand
>> "failed to update qgroup status and info\n");
>> err = btrfs_end_transaction(trans, root);
>> if (err && !ret)
next prev parent reply other threads:[~2016-05-01 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 4:22 [PATCH V2 RESEND] btrfs: pass the error code to the btrfs_std_error and log ret Anand Jain
2016-03-16 13:10 ` David Sterba
2016-05-01 23:06 ` Anand Jain [this message]
2016-05-02 15:14 ` David Sterba
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=57268BF5.7010408@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--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).