From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 4/5] xfs: use xfs_ilock_map_shared in xfs_attr_get
Date: Fri, 6 Dec 2013 07:59:10 +1100 [thread overview]
Message-ID: <20131205205910.GD29897@dastard> (raw)
In-Reply-To: <20131205155951.679310054@bombadil.infradead.org>
On Thu, Dec 05, 2013 at 07:58:34AM -0800, Christoph Hellwig wrote:
> We might not have read in the extent list at this point, so make sure we
> take the ilock exclusively if we have to do so.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> diff --git a/fs/xfs/xfs_attr.c b/fs/xfs/xfs_attr.c
> index b861270..5343034 100644
> --- a/fs/xfs/xfs_attr.c
> +++ b/fs/xfs/xfs_attr.c
> @@ -164,6 +164,7 @@ xfs_attr_get(
> {
> int error;
> struct xfs_name xname;
> + uint lock_mode;
>
> XFS_STATS_INC(xs_attr_get);
>
> @@ -174,9 +175,9 @@ xfs_attr_get(
> if (error)
> return error;
>
> - xfs_ilock(ip, XFS_ILOCK_SHARED);
> + lock_mode = xfs_ilock_map_shared(ip);
> error = xfs_attr_get_int(ip, &xname, value, valuelenp, flags);
> - xfs_iunlock(ip, XFS_ILOCK_SHARED);
> + xfs_iunlock_map_shared(ip, lock_mode);
> return(error);
> }
I think the locking here should be moved inside xfs_attr_get_int()
so that it uses the same locking pattern as xfs_attr_set() and
xfs_attr_remove().
Also, xfs_attr_list() needs this treatment (the attr version of
readdir) as well (and it has the locking inside xfs_attr_list_int(),
too ;).
It looks like xfs_readlink needs fixing, too.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-05 20:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 15:58 [PATCH 0/5] extent list locking fixes Christoph Hellwig
2013-12-05 15:58 ` [PATCH 1/5] xfs: take the ilock around xfs_bmapi_read in xfs_zero_remaining_bytes Christoph Hellwig
2013-12-05 19:38 ` Ben Myers
2013-12-05 20:31 ` Dave Chinner
2013-12-05 20:37 ` Ben Myers
2013-12-05 20:40 ` Christoph Hellwig
2013-12-05 15:58 ` [PATCH 2/5] xfs: use xfs_ilock_map_shared in xfs_qm_dqtobp Christoph Hellwig
2013-12-05 19:46 ` Ben Myers
2013-12-05 20:41 ` Dave Chinner
2013-12-05 20:53 ` Christoph Hellwig
2013-12-05 21:03 ` Dave Chinner
2013-12-05 15:58 ` [PATCH 3/5] xfs: use xfs_ilock_map_shared in xfs_qm_dqiterate Christoph Hellwig
2013-12-05 19:48 ` Ben Myers
2013-12-05 20:45 ` Dave Chinner
2013-12-05 15:58 ` [PATCH 4/5] xfs: use xfs_ilock_map_shared in xfs_attr_get Christoph Hellwig
2013-12-05 19:57 ` Ben Myers
2013-12-05 20:59 ` Dave Chinner [this message]
2013-12-05 21:01 ` Christoph Hellwig
2013-12-05 21:05 ` Dave Chinner
2013-12-05 21:10 ` Christoph Hellwig
2013-12-05 21:17 ` Dave Chinner
2013-12-05 15:58 ` [PATCH 5/5] xfs: assert that we hold the ilock for extent map access Christoph Hellwig
2013-12-05 20:11 ` Ben Myers
2013-12-05 21:10 ` Dave Chinner
2013-12-05 21:22 ` Christoph Hellwig
2013-12-05 21:40 ` Dave Chinner
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=20131205205910.GD29897@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.