public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanrlinux@gmail.com>
To: Allison Henderson <allison.henderson@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v17 05/11] xfs: Separate xfs_attr_node_addname and xfs_attr_node_addname_clear_incomplete
Date: Tue, 20 Apr 2021 17:44:26 +0530	[thread overview]
Message-ID: <875z0hxie5.fsf@garuda> (raw)
In-Reply-To: <a83a5de6-2e6c-c4ec-12cd-b99522e83bc8@oracle.com>

On 20 Apr 2021 at 00:02, Allison Henderson wrote:
> On 4/18/21 10:15 PM, Chandan Babu R wrote:
>> On 16 Apr 2021 at 14:50, Allison Henderson wrote:
>>> This patch separate xfs_attr_node_addname into two functions.  This will
>>> help to make it easier to hoist parts of xfs_attr_node_addname that need
>>> state management
>>>
>>> Signed-off-by: Allison Henderson <allison.henderson@oracle.com>
>>> Reviewed-by: Brian Foster <bfoster@redhat.com>
>>> ---
>>>   fs/xfs/libxfs/xfs_attr.c | 20 ++++++++++++++++++++
>>>   1 file changed, 20 insertions(+)
>>>
>>> diff --git a/fs/xfs/libxfs/xfs_attr.c b/fs/xfs/libxfs/xfs_attr.c
>>> index fff1c6f..d9dfc8d2 100644
>>> --- a/fs/xfs/libxfs/xfs_attr.c
>>> +++ b/fs/xfs/libxfs/xfs_attr.c
>>> @@ -54,6 +54,7 @@ STATIC int xfs_attr_leaf_hasname(struct xfs_da_args *args, struct xfs_buf **bp);
>>>   STATIC int xfs_attr_node_get(xfs_da_args_t *args);
>>>   STATIC int xfs_attr_node_addname(xfs_da_args_t *args);
>>>   STATIC int xfs_attr_node_removename(xfs_da_args_t *args);
>>> +STATIC int xfs_attr_node_addname_clear_incomplete(struct xfs_da_args *args);
>>>   STATIC int xfs_attr_node_hasname(xfs_da_args_t *args,
>>>   				 struct xfs_da_state **state);
>>>   STATIC int xfs_attr_fillstate(xfs_da_state_t *state);
>>> @@ -1062,6 +1063,25 @@ xfs_attr_node_addname(
>>>   			return error;
>>>   	}
>>>
>>> +	error = xfs_attr_node_addname_clear_incomplete(args);
> Ok, so i think what we need here is an extra few lines below.  That's
> similar to the original exit handling
>
> 	if (error)
> 		goto out;
> 	retval = error = 0;

        "retval = 0;" should suffice.
        
>
> Looks good?
>
>>> +out:
>>> +	if (state)
>>> +		xfs_da_state_free(state);
>>> +	if (error)
>>> +		return error;
>>> +	return retval;
>>
>> I think the above code incorrectly returns -ENOSPC when the user is performing
>> an xattr rename operation and the call to xfs_attr3_leaf_add() resulted in
>> returning -ENOSPC,
>> 1. xfs_attr3_leaf_add() returns -ENOSPC.
>> 2. xfs_da3_split() allocates a new leaf and inserts the new xattr into it.
>> 3. If the user was performing a rename operation (i.e. XFS_DA_OP_RENAME is
>>     set), we flip the "incomplete" flag.
>> 4. Remove the old xattr's remote blocks (if any).
>> 5. Remove old xattr's name.
>> 6. If "error" has zero as its value, we return the value of "retval". At this
>>     point in execution, "retval" would have -ENOSPC as its value.
>>
> Thanks for the catch!
> Allison

-- 
chandan

  reply	other threads:[~2021-04-20 12:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  9:20 [PATCH v17 00/11] xfs: Delay Ready Attributes Allison Henderson
2021-04-16  9:20 ` [PATCH v17 01/11] xfs: Reverse apply 72b97ea40d Allison Henderson
2021-04-16  9:20 ` [PATCH v17 02/11] xfs: Add xfs_attr_node_remove_cleanup Allison Henderson
2021-04-16  9:20 ` [PATCH v17 03/11] xfs: Hoist xfs_attr_set_shortform Allison Henderson
2021-04-16  9:20 ` [PATCH v17 04/11] xfs: Add helper xfs_attr_set_fmt Allison Henderson
2021-04-16  9:20 ` [PATCH v17 05/11] xfs: Separate xfs_attr_node_addname and xfs_attr_node_addname_clear_incomplete Allison Henderson
2021-04-19  5:15   ` Chandan Babu R
2021-04-19 18:32     ` Allison Henderson
2021-04-20 12:14       ` Chandan Babu R [this message]
2021-04-20 17:41         ` Allison Henderson
2021-04-16  9:20 ` [PATCH v17 06/11] xfs: Add helper xfs_attr_node_addname_find_attr Allison Henderson
2021-04-16  9:20 ` [PATCH v17 07/11] xfs: Hoist xfs_attr_node_addname Allison Henderson
2021-04-19  5:31   ` Chandan Babu R
2021-04-19 18:32     ` Allison Henderson
2021-04-16  9:20 ` [PATCH v17 08/11] xfs: Hoist xfs_attr_leaf_addname Allison Henderson
2021-04-23 17:06   ` Brian Foster
2021-04-24  3:26     ` Allison Henderson
2021-04-16  9:20 ` [PATCH v17 09/11] xfs: Hoist node transaction handling Allison Henderson
2021-04-16  9:20 ` [PATCH v17 10/11] xfs: Add delay ready attr remove routines Allison Henderson
2021-04-19  6:53   ` Chandan Babu R
2021-04-19 18:32     ` Allison Henderson
2021-04-23 17:06   ` Brian Foster
2021-04-24  3:27     ` Allison Henderson
2021-04-24 15:56       ` Darrick J. Wong
2021-04-26 11:49         ` Brian Foster
2021-04-26 16:52           ` Allison Henderson
2021-04-16  9:20 ` [PATCH v17 11/11] xfs: Add delay ready attr set routines Allison Henderson
2021-04-23 19:08   ` Brian Foster
2021-04-24  3:27     ` Allison Henderson

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=875z0hxie5.fsf@garuda \
    --to=chandanrlinux@gmail.com \
    --cc=allison.henderson@oracle.com \
    --cc=linux-xfs@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