public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com
Subject: Re: [PATCH V6 13/17] xfs: xfs_growfs_rt_alloc: Unlock inode explicitly rather than through iop_committing()
Date: Thu, 24 Feb 2022 21:06:10 -0800	[thread overview]
Message-ID: <20220225050610.GQ8313@magnolia> (raw)
In-Reply-To: <20220224130211.1346088-14-chandan.babu@oracle.com>

On Thu, Feb 24, 2022 at 06:32:07PM +0530, Chandan Babu R wrote:
> In order to be able to upgrade inodes to XFS_DIFLAG2_NREXT64, a future commit
> will perform such an upgrade in a transaction context. This requires the
> transaction to be rolled once. Hence inodes which have been added to the
> tranasction (via xfs_trans_ijoin()) with non-zero value for lock_flags
> argument would cause the inode to be unlocked when the transaction is rolled.
> 
> To prevent this from happening in the case of realtime bitmap/summary inodes,
> this commit now unlocks the inode explictly rather than through
> iop_committing() call back.
> 
> Signed-off-by: Chandan Babu R <chandan.babu@oracle.com>
> ---
>  fs/xfs/xfs_rtalloc.c | 12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/xfs/xfs_rtalloc.c b/fs/xfs/xfs_rtalloc.c
> index b8c79ee791af..379ef99722c5 100644
> --- a/fs/xfs/xfs_rtalloc.c
> +++ b/fs/xfs/xfs_rtalloc.c
> @@ -780,6 +780,7 @@ xfs_growfs_rt_alloc(
>  	int			resblks;	/* space reservation */
>  	enum xfs_blft		buf_type;
>  	struct xfs_trans	*tp;
> +	bool			unlock_inode;
>  
>  	if (ip == mp->m_rsumip)
>  		buf_type = XFS_BLFT_RTSUMMARY_BUF;
> @@ -802,7 +803,8 @@ xfs_growfs_rt_alloc(
>  		 * Lock the inode.
>  		 */
>  		xfs_ilock(ip, XFS_ILOCK_EXCL);
> -		xfs_trans_ijoin(tp, ip, XFS_ILOCK_EXCL);
> +		xfs_trans_ijoin(tp, ip, 0);
> +		unlock_inode = true;

Hmm.  Eventually you could replace all this with a single call to
xfs_trans_alloc_inode, which would fix the quota leak from the rt
metadata file expansion:

https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?h=realtime-quotas&id=c82a57844b60bb434103eacf757e47417f94a631

However, as rt+quota are not a supported feature, I'll let that lie for
now.

>  
>  		error = xfs_iext_count_may_overflow(ip, XFS_DATA_FORK,
>  				XFS_IEXT_ADD_NOSPLIT_CNT);
> @@ -824,7 +826,11 @@ xfs_growfs_rt_alloc(
>  		 */
>  		error = xfs_trans_commit(tp);
>  		if (error)
> -			return error;
> +			goto out_trans_cancel;

xfs_trans_commit frees tp even if the commit fails, which means that it
is not correct to call xfs_trans_cancel on tp here.  I think you could
do:

		error = xfs_trans_commit(tp);
		unlock_inode = false;
		xfs_iunlock(ip, XFS_ILOCK_EXCL);
		if (error)
			return error;

Right?

--D

> +
> +		unlock_inode = false;
> +		xfs_iunlock(ip, XFS_ILOCK_EXCL);
> +
>  		/*
>  		 * Now we need to clear the allocated blocks.
>  		 * Do this one block per transaction, to keep it simple.
> @@ -874,6 +880,8 @@ xfs_growfs_rt_alloc(
>  
>  out_trans_cancel:
>  	xfs_trans_cancel(tp);
> +	if (unlock_inode)
> +		xfs_iunlock(ip, XFS_ILOCK_EXCL);
>  	return error;
>  }
>  
> -- 
> 2.30.2
> 

  reply	other threads:[~2022-02-25  5:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 13:01 [PATCH V6 00/17] xfs: Extend per-inode extent counters Chandan Babu R
2022-02-24 13:01 ` [PATCH V6 01/17] xfs: Move extent count limits to xfs_format.h Chandan Babu R
2022-02-24 13:01 ` [PATCH V6 02/17] xfs: Introduce xfs_iext_max_nextents() helper Chandan Babu R
2022-02-24 13:01 ` [PATCH V6 03/17] xfs: Use xfs_extnum_t instead of basic data types Chandan Babu R
2022-02-24 13:01 ` [PATCH V6 04/17] xfs: Introduce xfs_dfork_nextents() helper Chandan Babu R
2022-02-24 13:01 ` [PATCH V6 05/17] xfs: Use basic types to define xfs_log_dinode's di_nextents and di_anextents Chandan Babu R
2022-02-24 13:02 ` [PATCH V6 06/17] xfs: Promote xfs_extnum_t and xfs_aextnum_t to 64 and 32-bits respectively Chandan Babu R
2022-02-24 13:02 ` [PATCH V6 07/17] xfs: Introduce XFS_SB_FEAT_INCOMPAT_NREXT64 and associated per-fs feature bit Chandan Babu R
2022-02-24 13:02 ` [PATCH V6 08/17] xfs: Introduce XFS_FSOP_GEOM_FLAGS_NREXT64 Chandan Babu R
2022-02-24 13:02 ` [PATCH V6 09/17] xfs: Introduce XFS_DIFLAG2_NREXT64 and associated helpers Chandan Babu R
2022-02-24 13:02 ` [PATCH V6 10/17] xfs: Use xfs_rfsblock_t to count maximum blocks that can be used by BMBT Chandan Babu R
2022-02-24 13:02 ` [PATCH V6 11/17] xfs: Introduce macros to represent new maximum extent counts for data/attr forks Chandan Babu R
2022-02-24 13:02 ` [PATCH V6 12/17] xfs: Introduce per-inode 64-bit extent counters Chandan Babu R
2022-02-25  4:58   ` Darrick J. Wong
2022-02-24 13:02 ` [PATCH V6 13/17] xfs: xfs_growfs_rt_alloc: Unlock inode explicitly rather than through iop_committing() Chandan Babu R
2022-02-25  5:06   ` Darrick J. Wong [this message]
2022-02-25  6:13     ` Chandan Babu R
2022-02-24 13:02 ` [PATCH V6 14/17] xfs: Conditionally upgrade existing inodes to use 64-bit extent counters Chandan Babu R
2022-02-25  5:11   ` Darrick J. Wong
2022-02-24 13:02 ` [PATCH V6 15/17] xfs: Enable bulkstat ioctl to support 64-bit per-inode " Chandan Babu R
2022-02-25  5:10   ` Darrick J. Wong
2022-02-25  6:59     ` Chandan Babu R
2022-02-24 13:02 ` [PATCH V6 16/17] xfs: Add XFS_SB_FEAT_INCOMPAT_NREXT64 to the list of supported flags Chandan Babu R
2022-02-24 13:02 ` [PATCH V6 17/17] xfs: Define max extent length based on on-disk format definition Chandan Babu R

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=20220225050610.GQ8313@magnolia \
    --to=djwong@kernel.org \
    --cc=chandan.babu@oracle.com \
    --cc=david@fromorbit.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