From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: remove racy hasattr check from attr ops
Date: Wed, 25 Jan 2017 07:55:26 -0800 [thread overview]
Message-ID: <20170125155526.GL9134@birch.djwong.org> (raw)
In-Reply-To: <20170125124411.GA28388@bfoster.bfoster>
On Wed, Jan 25, 2017 at 07:44:12AM -0500, Brian Foster wrote:
> On Mon, Jan 09, 2017 at 10:22:58AM -0500, Brian Foster wrote:
> > xfs_attr_[get|remove]() have unlocked attribute fork checks to optimize
> > away a lock cycle in cases where the fork does not exist or is otherwise
> > empty. This check is not safe, however, because an attribute fork short
> > form to extent format conversion includes a transient state that causes
> > the xfs_inode_hasattr() check to fail. Specifically,
> > xfs_attr_shortform_to_leaf() creates an empty extent format attribute
> > fork and then adds the existing shortform attributes to it.
> >
> > This means that lookup of an existing xattr can spuriously return
> > -ENOATTR when racing against a setxattr that causes the associated
> > format conversion. This was originally reproduced by an untar on a
> > particularly configured glusterfs volume, but can also be reproduced on
> > demand with properly crafted xattr requests.
> >
> > The format conversion occurs under the exclusive ilock. xfs_attr_get()
> > and xfs_attr_remove() already have the proper locking and checks further
> > down in the functions to handle this situation correctly. Drop the
> > unlocked checks to avoid the spurious failure and rely on the existing
> > logic.
> >
> > Signed-off-by: Brian Foster <bfoster@redhat.com>
> > ---
> >
>
> Ping. Any chance of getting this one in soonish?
Yep, I'm queueing it up for -rc6. Sorry for the delay.
--D
>
> Brian
>
> > v2:
> > - Fix up xfs_attr_remove() as well.
> > v1: https://patchwork.kernel.org/patch/9501675/
> >
> > fs/xfs/libxfs/xfs_attr.c | 6 ------
> > 1 file changed, 6 deletions(-)
> >
> > diff --git a/fs/xfs/libxfs/xfs_attr.c b/fs/xfs/libxfs/xfs_attr.c
> > index af1ecb1..6622d46 100644
> > --- a/fs/xfs/libxfs/xfs_attr.c
> > +++ b/fs/xfs/libxfs/xfs_attr.c
> > @@ -131,9 +131,6 @@ xfs_attr_get(
> > if (XFS_FORCED_SHUTDOWN(ip->i_mount))
> > return -EIO;
> >
> > - if (!xfs_inode_hasattr(ip))
> > - return -ENOATTR;
> > -
> > error = xfs_attr_args_init(&args, ip, name, flags);
> > if (error)
> > return error;
> > @@ -392,9 +389,6 @@ xfs_attr_remove(
> > if (XFS_FORCED_SHUTDOWN(dp->i_mount))
> > return -EIO;
> >
> > - if (!xfs_inode_hasattr(dp))
> > - return -ENOATTR;
> > -
> > error = xfs_attr_args_init(&args, dp, name, flags);
> > if (error)
> > return error;
> > --
> > 2.7.4
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-xfs" 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-xfs" 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:[~2017-01-25 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 15:22 [PATCH v2] xfs: remove racy hasattr check from attr ops Brian Foster
2017-01-09 15:54 ` Christoph Hellwig
2017-01-25 12:44 ` Brian Foster
2017-01-25 15:55 ` Darrick J. Wong [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=20170125155526.GL9134@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.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;
as well as URLs for NNTP newsgroup(s).