xfs
[Top] [All Lists]

Re: [PATCH 2/4] xfs: set up inode operation vectors later

To: Christoph Hellwig <hch@xxxxxx>
Subject: Re: [PATCH 2/4] xfs: set up inode operation vectors later
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 24 Mar 2016 10:05:00 +1100
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1458740935-31260-3-git-send-email-hch@xxxxxx>
References: <1458740935-31260-1-git-send-email-hch@xxxxxx> <1458740935-31260-3-git-send-email-hch@xxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, Mar 23, 2016 at 02:48:53PM +0100, Christoph Hellwig wrote:
> In the next patch we'll set up different inode operations for inline vs
> out of line symlinks, for that we need to make sure the flags are already
> set up properly.
....
> diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c
> index fb7dc61..f08d91c 100644
> --- a/fs/xfs/xfs_iops.c
> +++ b/fs/xfs/xfs_iops.c
> @@ -181,6 +181,8 @@ xfs_generic_create(
>       }
>  #endif
>  
> +     xfs_setup_iops(ip);
> +
>       if (tmpfile)
>               d_tmpfile(dentry, inode);
>       else
> @@ -368,6 +370,8 @@ xfs_vn_symlink(
>       if (unlikely(error))
>               goto out_cleanup_inode;
>  
> +     xfs_setup_iops(cip);
> +
>       d_instantiate(dentry, inode);
>       xfs_finish_inode_setup(cip);

I think there are more places than this that need xfs_setup_iops()
calls - a quick look around makes me think they need to be paired
with every path that calls xfs_finish_inode_setup().

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>