Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: linux-xfs@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Carlos Maiolino <cem@kernel.org>,
	Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH v2 1/4] xfs: add xfs_metadir_create_file helper
Date: Mon, 13 Jul 2026 15:51:42 -0700	[thread overview]
Message-ID: <20260713225142.GI7195@frogsfrogsfrogs> (raw)
In-Reply-To: <20260713124250.3978-2-johannes.thumshirn@wdc.com>

On Mon, Jul 13, 2026 at 02:42:47PM +0200, Johannes Thumshirn wrote:
> Factor the metadata inode create/commit/cleanup lifecycle out of
> xfs_metadir_mkdir into a reusable helper that takes an optional callback
> to initialize the new inode, and convert xfs_metadir_mkdir to it.
> 
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> ---
>  fs/xfs/libxfs/xfs_metadir.c | 58 +++++++++++++++++++++++--------------
>  fs/xfs/libxfs/xfs_metadir.h |  6 ++++
>  2 files changed, 43 insertions(+), 21 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_metadir.c b/fs/xfs/libxfs/xfs_metadir.c
> index 74c4596ee4cf..0d6a153bc9e9 100644
> --- a/fs/xfs/libxfs/xfs_metadir.c
> +++ b/fs/xfs/libxfs/xfs_metadir.c
> @@ -438,48 +438,64 @@ xfs_metadir_cancel(
>  	xfs_metadir_teardown(upd, error);
>  }
>  
> -/* Create a metadata for the last component of the path. */
>  int
> -xfs_metadir_mkdir(
> -	struct xfs_inode		*dp,
> -	const char			*path,
> +xfs_metadir_create_file(
> +	struct xfs_metadir_update	*upd,
> +	umode_t				mode,
> +	xfs_metadir_createfn		create,
> +	void				*priv,
>  	struct xfs_inode		**ipp)
>  {
> -	struct xfs_metadir_update	upd = {
> -		.dp			= dp,
> -		.path			= path,
> -		.metafile_type		= XFS_METAFILE_DIR,
> -	};
>  	int				error;
>  
> -	if (xfs_is_shutdown(dp->i_mount))
> +	if (xfs_is_shutdown(upd->dp->i_mount))
>  		return -EIO;
>  
> -	/* Allocate a transaction to create the last directory. */
> -	error = xfs_metadir_start_create(&upd);
> +	error = xfs_metadir_start_create(upd);
>  	if (error)
>  		return error;
>  
> -	/* Create the subdirectory and take our reference. */
> -	error = xfs_metadir_create(&upd, S_IFDIR);
> +	error = xfs_metadir_create(upd, mode);
>  	if (error)
>  		goto out_cancel;
>  
> -	error = xfs_metadir_commit(&upd);
> +	if (create) {
> +		error = create(upd, priv);
> +		if (error)
> +			goto out_cancel;
> +	}
> +
> +	error = xfs_metadir_commit(upd);
>  	if (error)
>  		goto out_irele;
>  
> -	xfs_finish_inode_setup(upd.ip);
> -	*ipp = upd.ip;
> +	xfs_finish_inode_setup(upd->ip);
> +	*ipp = upd->ip;
>  	return 0;
>  
>  out_cancel:
> -	xfs_metadir_cancel(&upd, error);
> +	xfs_metadir_cancel(upd, error);
>  out_irele:
>  	/* Have to finish setting up the inode to ensure it's deleted. */
> -	if (upd.ip) {
> -		xfs_finish_inode_setup(upd.ip);
> -		xfs_irele(upd.ip);
> +	if (upd->ip) {
> +		xfs_finish_inode_setup(upd->ip);
> +		xfs_irele(upd->ip);
>  	}
>  	return error;
>  }
> +
> +/* Create a metadata for the last component of the path. */
> +int
> +xfs_metadir_mkdir(
> +	struct xfs_inode		*dp,
> +	const char			*path,
> +	struct xfs_inode		**ipp)
> +{
> +	struct xfs_metadir_update	upd = {
> +		.dp			= dp,
> +		.path			= path,
> +		.metafile_type		= XFS_METAFILE_DIR,
> +	};
> +
> +	return xfs_metadir_create_file(&upd, S_IFDIR, NULL, NULL, ipp);
> +}
> diff --git a/fs/xfs/libxfs/xfs_metadir.h b/fs/xfs/libxfs/xfs_metadir.h
> index bfecac7d3d14..a795a2d0e3fe 100644
> --- a/fs/xfs/libxfs/xfs_metadir.h
> +++ b/fs/xfs/libxfs/xfs_metadir.h
> @@ -35,6 +35,12 @@ int xfs_metadir_load(struct xfs_trans *tp, struct xfs_inode *dp,
>  int xfs_metadir_start_create(struct xfs_metadir_update *upd);
>  int xfs_metadir_create(struct xfs_metadir_update *upd, umode_t mode);
>  
> +typedef int (*xfs_metadir_createfn)(struct xfs_metadir_update *upd, void *priv);
> +
> +int xfs_metadir_create_file(struct xfs_metadir_update *upd, umode_t mode,
> +		xfs_metadir_createfn create, void *priv,

I'd have called these both "_create_fn" and "create_fn" for consistency
but otherwise this looks fine to me.

Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> +		struct xfs_inode **ipp);
> +
>  int xfs_metadir_start_link(struct xfs_metadir_update *upd);
>  int xfs_metadir_link(struct xfs_metadir_update *upd);
>  
> -- 
> 2.54.0
> 
> 

  parent reply	other threads:[~2026-07-13 22:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 12:42 [PATCH v2 0/4] xfs: consolidate metadir creation code Johannes Thumshirn
2026-07-13 12:42 ` [PATCH v2 1/4] xfs: add xfs_metadir_create_file helper Johannes Thumshirn
2026-07-13 13:31   ` Christoph Hellwig
2026-07-13 22:51   ` Darrick J. Wong [this message]
2026-07-13 12:42 ` [PATCH v2 2/4] xfs: create quota metadir inodes using xfs_metadir_create_file Johannes Thumshirn
2026-07-13 22:52   ` Darrick J. Wong
2026-07-13 12:42 ` [PATCH v2 3/4] xfs: create rtgroup " Johannes Thumshirn
2026-07-13 22:54   ` Darrick J. Wong
2026-07-13 12:42 ` [PATCH v2 4/4] xfs: mark internal metadir file creation helpers static Johannes Thumshirn
2026-07-13 13:32   ` Christoph Hellwig
2026-07-13 22:55   ` Darrick J. Wong

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=20260713225142.GI7195@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=johannes.thumshirn@wdc.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