Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xiakaixu1987@gmail.com
Cc: linux-xfs@vger.kernel.org, Kaixu Xia <kaixuxia@tencent.com>
Subject: Re: [PATCH v2] xfs: directly call xfs_generic_create() for ->create() and ->mkdir()
Date: Fri, 25 Sep 2020 11:14:44 -0700	[thread overview]
Message-ID: <20200925181444.GN7955@magnolia> (raw)
In-Reply-To: <1601001801-25508-1-git-send-email-kaixuxia@tencent.com>

On Fri, Sep 25, 2020 at 10:43:21AM +0800, xiakaixu1987@gmail.com wrote:
> From: Kaixu Xia <kaixuxia@tencent.com>
> 
> The current create and mkdir handlers both call the xfs_vn_mknod()
> which is a wrapper routine around xfs_generic_create() function.
> Actually the create and mkdir handlers can directly call
> xfs_generic_create() function and reduce the call chain.
> 
> Signed-off-by: Kaixu Xia <kaixuxia@tencent.com>

Looks good to me,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

--D

> ---
> v2:
>  -add the necessary space.
> 
>  fs/xfs/xfs_iops.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c
> index 80a13c8561d8..5e165456da68 100644
> --- a/fs/xfs/xfs_iops.c
> +++ b/fs/xfs/xfs_iops.c
> @@ -237,7 +237,7 @@ xfs_vn_create(
>  	umode_t		mode,
>  	bool		flags)
>  {
> -	return xfs_vn_mknod(dir, dentry, mode, 0);
> +	return xfs_generic_create(dir, dentry, mode, 0, false);
>  }
>  
>  STATIC int
> @@ -246,7 +246,7 @@ xfs_vn_mkdir(
>  	struct dentry	*dentry,
>  	umode_t		mode)
>  {
> -	return xfs_vn_mknod(dir, dentry, mode|S_IFDIR, 0);
> +	return xfs_generic_create(dir, dentry, mode | S_IFDIR, 0, false);
>  }
>  
>  STATIC struct dentry *
> -- 
> 2.20.0
> 

      reply	other threads:[~2020-09-25 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  2:43 [PATCH v2] xfs: directly call xfs_generic_create() for ->create() and ->mkdir() xiakaixu1987
2020-09-25 18:14 ` 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=20200925181444.GN7955@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=kaixuxia@tencent.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=xiakaixu1987@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox