public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/8 V2] libxfs: use a memory zone for transactions
Date: Thu, 25 Jan 2018 11:22:21 -0800	[thread overview]
Message-ID: <20180125192221.GM9068@magnolia> (raw)
In-Reply-To: <e8515b2e-094b-3092-d82c-3394bd5d0ec5@sandeen.net>

On Thu, Jan 25, 2018 at 01:01:19PM -0600, Eric Sandeen wrote:
> In addition to more closely matching the kernel, this will
> help us catch any leaks from these allocations.
> 
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>

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

> ---
> 
> V2: remove pointless NULL assignments
> 
> diff --git a/libxfs/init.c b/libxfs/init.c
> index 302f088..7bde8b7 100644
> --- a/libxfs/init.c
> +++ b/libxfs/init.c
> @@ -384,6 +384,7 @@ manage_zones(int release)
>  	extern kmem_zone_t	*xfs_da_state_zone;
>  	extern kmem_zone_t	*xfs_btree_cur_zone;
>  	extern kmem_zone_t	*xfs_bmap_free_item_zone;
> +	extern kmem_zone_t	*xfs_trans_zone;
>  	extern kmem_zone_t	*xfs_log_item_desc_zone;
>  	extern void		xfs_dir_startup();
>  
> @@ -395,6 +396,7 @@ manage_zones(int release)
>  		kmem_free(xfs_da_state_zone);
>  		kmem_free(xfs_btree_cur_zone);
>  		kmem_free(xfs_bmap_free_item_zone);
> +		kmem_free(xfs_trans_zone);
>  		kmem_free(xfs_log_item_desc_zone);
>  		return;
>  	}
> @@ -413,6 +415,8 @@ manage_zones(int release)
>  	xfs_bmap_free_item_zone = kmem_zone_init(
>  			sizeof(struct xfs_extent_free_item),
>  			"xfs_bmap_free_item");
> +	xfs_trans_zone = kmem_zone_init(
> +			sizeof(struct xfs_trans), "xfs_trans");
>  	xfs_log_item_desc_zone = kmem_zone_init(
>  			sizeof(struct xfs_log_item_desc), "xfs_log_item_desc");
>  	xfs_dir_startup();
> diff --git a/libxfs/trans.c b/libxfs/trans.c
> index 57ff3ea..a602eaa 100644
> --- a/libxfs/trans.c
> +++ b/libxfs/trans.c
> @@ -36,6 +36,7 @@ static void xfs_trans_free_items(struct xfs_trans *tp);
>   * Simple transaction interface
>   */
>  
> +kmem_zone_t	*xfs_trans_zone;
>  kmem_zone_t	*xfs_log_item_desc_zone;
>  
>  /*
> @@ -143,6 +144,17 @@ libxfs_trans_roll(
>  	return 0;
>  }
>  
> +/*
> + * Free the transaction structure.  If there is more clean up
> + * to do when the structure is freed, add it here.
> + */
> +static void
> +xfs_trans_free(
> +	struct xfs_trans	*tp)
> +{
> +	kmem_zone_free(xfs_trans_zone, tp);
> +}
> +
>  int
>  libxfs_trans_alloc(
>  	struct xfs_mount	*mp,
> @@ -166,11 +178,8 @@ libxfs_trans_alloc(
>  			return -ENOSPC;
>  	}
>  
> -	if ((ptr = calloc(sizeof(xfs_trans_t), 1)) == NULL) {
> -		fprintf(stderr, _("%s: xact calloc failed (%d bytes): %s\n"),
> -			progname, (int)sizeof(xfs_trans_t), strerror(errno));
> -		exit(1);
> -	}
> +	ptr = kmem_zone_zalloc(xfs_trans_zone,
> +		(flags & XFS_TRANS_NOFS) ? KM_NOFS : KM_SLEEP);
>  	ptr->t_mountp = mp;
>  	ptr->t_blk_res = blocks;
>  	INIT_LIST_HEAD(&ptr->t_items);
> @@ -212,8 +221,7 @@ libxfs_trans_cancel(
>  #endif
>  	if (tp != NULL) {
>  		xfs_trans_free_items(tp);
> -		free(tp);
> -		tp = NULL;
> +		xfs_trans_free(tp);
>  	}
>  #ifdef XACT_DEBUG
>  	fprintf(stderr, "## cancelled transaction %p\n", otp);
> @@ -867,8 +875,7 @@ libxfs_trans_commit(
>  		fprintf(stderr, "committed clean transaction %p\n", tp);
>  #endif
>  		xfs_trans_free_items(tp);
> -		free(tp);
> -		tp = NULL;
> +		xfs_trans_free(tp);
>  		return 0;
>  	}
>  
> @@ -891,7 +898,6 @@ libxfs_trans_commit(
>  	trans_committed(tp);
>  
>  	/* That's it for the transaction structure.  Free it. */
> -	free(tp);
> -	tp = NULL;
> +	xfs_trans_free(tp);
>  	return 0;
>  }
> 
> --
> 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

  reply	other threads:[~2018-01-25 19:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 19:37 [PATCH 0/8] libxfs: cleanup & leak detection Eric Sandeen
2018-01-11 19:37 ` [PATCH 1/8] xfs: remove wrappers around b_fspriv Eric Sandeen
2018-01-11 19:42   ` Darrick J. Wong
2018-01-11 19:37 ` [PATCH 2/8] xfs: add a proper transaction pointer to struct xfs_buf Eric Sandeen
2018-01-11 19:43   ` Darrick J. Wong
2018-01-11 19:37 ` [PATCH 3/8] xfs: remove unused buf_fsprivate3 Eric Sandeen
2018-01-11 19:44   ` Darrick J. Wong
2018-01-11 19:37 ` [PATCH 4/8] libxfs: use a memory zone for transactions Eric Sandeen
2018-01-11 19:48   ` Darrick J. Wong
2018-01-25 19:01   ` [PATCH 4/8 V2] " Eric Sandeen
2018-01-25 19:22     ` Darrick J. Wong [this message]
2018-01-11 19:37 ` [PATCH 5/8] libxfs: use a memory zone for log items Eric Sandeen
2018-01-11 19:49   ` Darrick J. Wong
2018-01-11 19:37 ` [PATCH 6/8] libxfs: manage xfs_buf_zone count within cache Eric Sandeen
2018-01-11 20:20   ` Darrick J. Wong
2018-01-11 20:48     ` Eric Sandeen
2018-01-11 22:09       ` Dave Chinner
2018-01-11 19:37 ` [PATCH 7/8] libxfs: add function to free all bufferse in bcache Eric Sandeen
2018-01-11 20:05   ` Darrick J. Wong
2018-01-11 20:11     ` Eric Sandeen
2018-01-11 20:22       ` Darrick J. Wong
2018-01-11 19:37 ` [PATCH 8/8] libxfs: Catch non-empty zones on destroy Eric Sandeen
2018-01-11 20:29   ` Darrick J. Wong
2018-01-11 23:42     ` Eric Sandeen

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=20180125192221.GM9068@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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