From: Brian Foster <bfoster@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 08/11] xfs: move transaction handling to xfs_bmapi_convert_delalloc
Date: Thu, 31 Jan 2019 14:28:53 -0500 [thread overview]
Message-ID: <20190131192853.GJ36239@bfoster> (raw)
In-Reply-To: <20190131075524.4769-9-hch@lst.de>
On Thu, Jan 31, 2019 at 08:55:21AM +0100, Christoph Hellwig wrote:
> No need to deal with the transaction and the inode locking in the
> caller. Also move to automatic unlocking on transaction commit or
> cancel to simplify the code a little more.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/xfs/libxfs/xfs_bmap.c | 33 +++++++++++++++++++++++++++++----
> fs/xfs/libxfs/xfs_bmap.h | 6 +++---
> fs/xfs/xfs_iomap.c | 32 ++++----------------------------
> 3 files changed, 36 insertions(+), 35 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c
> index 818cd018d510..408a6da14849 100644
> --- a/fs/xfs/libxfs/xfs_bmap.c
> +++ b/fs/xfs/libxfs/xfs_bmap.c
> @@ -4446,16 +4446,32 @@ xfs_bmapi_write(
> */
> int
> xfs_bmapi_convert_delalloc(
> - struct xfs_trans *tp,
> struct xfs_inode *ip,
> int whichfork,
> xfs_fileoff_t offset_fsb,
> - struct xfs_bmbt_irec *imap)
> + struct xfs_bmbt_irec *imap,
> + unsigned int *seq)
> {
> struct xfs_ifork *ifp = XFS_IFORK_PTR(ip, whichfork);
> + struct xfs_mount *mp = ip->i_mount;
> struct xfs_bmalloca bma = { NULL };
> + struct xfs_trans *tp;
> int error;
>
> + /*
> + * Space for the extent and indirect blocks was reserved when the
> + * delalloc extent was created so there's no need to do so here.
> + */
> + error = xfs_trans_alloc(mp, &M_RES(mp)->tr_write, 0, 0,
> + XFS_TRANS_RESERVE, &tp);
> + if (error)
> + return error;
> +
> + xfs_ilock(ip, XFS_ILOCK_EXCL);
> + xfs_trans_ijoin(tp, ip, XFS_ILOCK_EXCL);
> +
> + *seq = READ_ONCE(ifp->if_seq);
> +
seq is going to change once we do the allocation. I think you want to
move this further down to where we set imap, otherwise looks good.
Brian
> if (!xfs_iext_lookup_extent(ip, ifp, offset_fsb, &bma.icur, &bma.got) ||
> bma.got.br_startoff > offset_fsb) {
> /*
> @@ -4464,7 +4480,8 @@ xfs_bmapi_convert_delalloc(
> * might have moved the extent to the data fork in the meantime.
> */
> WARN_ON_ONCE(whichfork != XFS_COW_FORK);
> - return -EAGAIN;
> + error = -EAGAIN;
> + goto out_trans_cancel;
> }
>
> /*
> @@ -4473,7 +4490,7 @@ xfs_bmapi_convert_delalloc(
> */
> if (!isnullstartblock(bma.got.br_startblock)) {
> *imap = bma.got;
> - return 0;
> + goto out_trans_cancel;
> }
>
> bma.tp = tp;
> @@ -4510,8 +4527,16 @@ xfs_bmapi_convert_delalloc(
>
> error = xfs_bmap_btree_to_extents(tp, ip, bma.cur, &bma.logflags,
> whichfork);
> + if (error)
> + goto out_finish;
> +
> + xfs_bmapi_finish(&bma, whichfork, 0);
> + return xfs_trans_commit(tp);
> +
> out_finish:
> xfs_bmapi_finish(&bma, whichfork, error);
> +out_trans_cancel:
> + xfs_trans_cancel(tp);
> return error;
> }
>
> diff --git a/fs/xfs/libxfs/xfs_bmap.h b/fs/xfs/libxfs/xfs_bmap.h
> index 5bdfa8001f07..78b190b6e908 100644
> --- a/fs/xfs/libxfs/xfs_bmap.h
> +++ b/fs/xfs/libxfs/xfs_bmap.h
> @@ -223,9 +223,9 @@ int xfs_bmapi_reserve_delalloc(struct xfs_inode *ip, int whichfork,
> xfs_fileoff_t off, xfs_filblks_t len, xfs_filblks_t prealloc,
> struct xfs_bmbt_irec *got, struct xfs_iext_cursor *cur,
> int eof);
> -int xfs_bmapi_convert_delalloc(struct xfs_trans *tp, struct xfs_inode *ip,
> - int whichfork, xfs_fileoff_t offset_fsb,
> - struct xfs_bmbt_irec *imap);
> +int xfs_bmapi_convert_delalloc(struct xfs_inode *ip, int whichfork,
> + xfs_fileoff_t offset_fsb, struct xfs_bmbt_irec *imap,
> + unsigned int *seq);
>
> static inline void
> xfs_bmap_add_free(
> diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
> index b7c1b279057b..39be741cac5a 100644
> --- a/fs/xfs/xfs_iomap.c
> +++ b/fs/xfs/xfs_iomap.c
> @@ -684,11 +684,9 @@ xfs_iomap_write_allocate(
> unsigned int *seq)
> {
> struct xfs_mount *mp = ip->i_mount;
> - struct xfs_ifork *ifp = XFS_IFORK_PTR(ip, whichfork);
> xfs_fileoff_t offset_fsb;
> xfs_fileoff_t map_start_fsb;
> xfs_extlen_t map_count_fsb;
> - struct xfs_trans *tp;
> int error = 0;
>
> /*
> @@ -716,17 +714,8 @@ xfs_iomap_write_allocate(
> /*
> * Allocate in a loop because it may take several attempts to
> * allocate real blocks for a contiguous delalloc extent if free
> - * space is sufficiently fragmented. Note that space for the
> - * extent and indirect blocks was reserved when the delalloc
> - * extent was created so there's no need to do so here.
> + * space is sufficiently fragmented.
> */
> - error = xfs_trans_alloc(mp, &M_RES(mp)->tr_write, 0, 0,
> - XFS_TRANS_RESERVE, &tp);
> - if (error)
> - return error;
> -
> - xfs_ilock(ip, XFS_ILOCK_EXCL);
> - xfs_trans_ijoin(tp, ip, 0);
>
> /*
> * ilock was dropped since imap was populated which means it
> @@ -737,17 +726,10 @@ xfs_iomap_write_allocate(
> * caller. We'll trim it down to the caller's most recently
> * validated range before we return.
> */
> - error = xfs_bmapi_convert_delalloc(tp, ip, whichfork,
> - offset_fsb, imap);
> - if (error)
> - goto trans_cancel;
> -
> - error = xfs_trans_commit(tp);
> + error = xfs_bmapi_convert_delalloc(ip, whichfork, offset_fsb,
> + imap, seq);
> if (error)
> - goto error0;
> -
> - *seq = READ_ONCE(ifp->if_seq);
> - xfs_iunlock(ip, XFS_ILOCK_EXCL);
> + return error;
>
> /*
> * See if we were able to allocate an extent that covers at
> @@ -766,12 +748,6 @@ xfs_iomap_write_allocate(
> return 0;
> }
> }
> -
> -trans_cancel:
> - xfs_trans_cancel(tp);
> -error0:
> - xfs_iunlock(ip, XFS_ILOCK_EXCL);
> - return error;
> }
>
> int
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-01-31 19:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 7:55 make delalloc conversion more robust and clear Christoph Hellwig
2019-01-31 7:55 ` [PATCH 01/11] FOLD: improve xfs_bmapi_delalloc Christoph Hellwig
2019-01-31 18:09 ` Brian Foster
2019-02-01 7:23 ` Christoph Hellwig
2019-02-01 7:28 ` Christoph Hellwig
2019-02-01 12:46 ` Brian Foster
2019-02-01 16:08 ` Christoph Hellwig
2019-01-31 7:55 ` [PATCH 02/11] xfs: remove the io_type field from the writeback context and ioend Christoph Hellwig
2019-01-31 18:10 ` Brian Foster
2019-01-31 7:55 ` [PATCH 03/11] xfs: remove the s_maxbytes checks in xfs_map_blocks Christoph Hellwig
2019-01-31 18:10 ` Brian Foster
2019-01-31 7:55 ` [PATCH 04/11] xfs: don't try to map blocks beyond i_size in writeback Christoph Hellwig
2019-01-31 18:11 ` Brian Foster
2019-02-01 7:25 ` Christoph Hellwig
2019-02-01 12:46 ` Brian Foster
2019-02-01 16:07 ` Christoph Hellwig
2019-01-31 7:55 ` [PATCH 05/11] xfs: simplify the xfs_bmap_btree_to_extents calling conventions Christoph Hellwig
2019-01-31 18:11 ` Brian Foster
2019-01-31 7:55 ` [PATCH 06/11] xfs: factor out two helpers from xfs_bmapi_write Christoph Hellwig
2019-01-31 18:28 ` Brian Foster
2019-01-31 7:55 ` [PATCH 07/11] xfs: split XFS_BMAPI_DELALLOC handling " Christoph Hellwig
2019-01-31 19:28 ` Brian Foster
2019-01-31 7:55 ` [PATCH 08/11] xfs: move transaction handling to xfs_bmapi_convert_delalloc Christoph Hellwig
2019-01-31 19:28 ` Brian Foster [this message]
2019-01-31 7:55 ` [PATCH 09/11] xfs: move stat accounting " Christoph Hellwig
2019-01-31 19:29 ` Brian Foster
2019-01-31 7:55 ` [PATCH 10/11] xfs: move xfs_iomap_write_allocate to xfs_aops.c Christoph Hellwig
2019-01-31 19:31 ` Brian Foster
2019-01-31 7:55 ` [PATCH 11/11] xfs: retry COW fork delalloc conversion when no extent was found Christoph Hellwig
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=20190131192853.GJ36239@bfoster \
--to=bfoster@redhat.com \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).