From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, hch@infradead.org, david@fromorbit.com
Subject: Re: [PATCH 10/12] xfs: make xfs_*read_agf return EAGAIN to ALLOC_FLAG_TRYLOCK callers
Date: Fri, 24 Jan 2020 15:12:07 -0800 [thread overview]
Message-ID: <20200124231207.GD20014@infradead.org> (raw)
In-Reply-To: <157984320125.3139258.966527323692871610.stgit@magnolia>
On Thu, Jan 23, 2020 at 09:20:01PM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Refactor xfs_read_agf and xfs_alloc_read_agf to return EAGAIN if the
> caller passed TRYLOCK and we weren't able to get the lock; and change
> the callers to recognize this.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> fs/xfs/libxfs/xfs_alloc.c | 36 ++++++++++++++----------------------
> fs/xfs/libxfs/xfs_bmap.c | 11 ++++++-----
> fs/xfs/xfs_filestream.c | 11 +++++------
> 3 files changed, 25 insertions(+), 33 deletions(-)
>
>
> diff --git a/fs/xfs/libxfs/xfs_alloc.c b/fs/xfs/libxfs/xfs_alloc.c
> index 34b65635ee34..d8053bc96c4d 100644
> --- a/fs/xfs/libxfs/xfs_alloc.c
> +++ b/fs/xfs/libxfs/xfs_alloc.c
> @@ -2502,12 +2502,11 @@ xfs_alloc_fix_freelist(
>
> if (!pag->pagf_init) {
> error = xfs_alloc_read_agf(mp, tp, args->agno, flags, &agbp);
> - if (error)
> + if (error) {
> + /* Couldn't lock the AGF so skip this AG. */
> + if (error == -EAGAIN)
> + error = 0;
> goto out_no_agbp;
> - if (!pag->pagf_init) {
> - ASSERT(flags & XFS_ALLOC_FLAG_TRYLOCK);
> - ASSERT(!(flags & XFS_ALLOC_FLAG_FREEING));
> - goto out_agbp_relse;
> }
> }
>
> @@ -2533,11 +2532,10 @@ xfs_alloc_fix_freelist(
> */
> if (!agbp) {
> error = xfs_alloc_read_agf(mp, tp, args->agno, flags, &agbp);
> - if (error)
> - goto out_no_agbp;
> - if (!agbp) {
> - ASSERT(flags & XFS_ALLOC_FLAG_TRYLOCK);
> - ASSERT(!(flags & XFS_ALLOC_FLAG_FREEING));
> + if (error) {
> + /* Couldn't lock the AGF so skip this AG. */
> + if (error == -EAGAIN)
> + error = 0;
> goto out_no_agbp;
> }
> }
> @@ -2768,11 +2766,10 @@ xfs_alloc_pagf_init(
> xfs_buf_t *bp;
> int error;
>
> - if ((error = xfs_alloc_read_agf(mp, tp, agno, flags, &bp)))
> - return error;
> - if (bp)
> + error = xfs_alloc_read_agf(mp, tp, agno, flags, &bp);
> + if (!error)
> xfs_trans_brelse(tp, bp);
> - return 0;
> + return error;
> }
>
> /*
> @@ -2961,12 +2958,6 @@ xfs_read_agf(
> error = xfs_trans_read_buf(mp, tp, mp->m_ddev_targp,
> XFS_AG_DADDR(mp, agno, XFS_AGF_DADDR(mp)),
> XFS_FSS_TO_BB(mp, 1), flags, bpp, &xfs_agf_buf_ops);
> - /*
> - * Callers of xfs_read_agf() currently interpret a NULL bpp as EAGAIN
> - * and need to be converted to check for EAGAIN specifically.
> - */
> - if (error == -EAGAIN)
> - return 0;
> if (error)
> return error;
>
> @@ -2992,14 +2983,15 @@ xfs_alloc_read_agf(
>
> trace_xfs_alloc_read_agf(mp, agno);
>
> + /* We don't support trylock when freeing. */
> + ASSERT((flags & (XFS_ALLOC_FLAG_FREEING | XFS_ALLOC_FLAG_TRYLOCK)) !=
> + (XFS_ALLOC_FLAG_FREEING | XFS_ALLOC_FLAG_TRYLOCK));
Does this assert really work? Shouldn't it be
ASSERT(!(flags & XFS_ALLOC_FLAG_FREEING) ||
!(flags & XFS_ALLOC_FLAG_TRYLOCK));
Otherwise looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2020-01-24 23:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 5:18 [PATCH v5 00/12] xfs: make buffer functions return error codes Darrick J. Wong
2020-01-24 5:19 ` [PATCH 01/12] xfs: make xfs_buf_alloc return an error code Darrick J. Wong
2020-01-24 5:19 ` [PATCH 02/12] xfs: make xfs_buf_get_map " Darrick J. Wong
2020-01-24 22:02 ` Dave Chinner
2020-01-24 22:59 ` Christoph Hellwig
2020-01-24 5:19 ` [PATCH 03/12] xfs: make xfs_buf_read_map " Darrick J. Wong
2020-01-24 22:05 ` Dave Chinner
2020-01-24 23:07 ` Christoph Hellwig
2020-01-24 5:19 ` [PATCH 04/12] xfs: make xfs_buf_get " Darrick J. Wong
2020-01-24 5:19 ` [PATCH 05/12] xfs: make xfs_buf_get_uncached " Darrick J. Wong
2020-01-24 5:19 ` [PATCH 06/12] xfs: make xfs_buf_read " Darrick J. Wong
2020-01-24 22:05 ` Dave Chinner
2020-01-24 23:08 ` Christoph Hellwig
2020-01-24 5:19 ` [PATCH 07/12] xfs: make xfs_trans_get_buf_map " Darrick J. Wong
2020-01-24 5:19 ` [PATCH 08/12] xfs: make xfs_trans_get_buf " Darrick J. Wong
2020-01-24 5:19 ` [PATCH 09/12] xfs: remove the xfs_btree_get_buf[ls] functions Darrick J. Wong
2020-01-24 5:20 ` [PATCH 10/12] xfs: make xfs_*read_agf return EAGAIN to ALLOC_FLAG_TRYLOCK callers Darrick J. Wong
2020-01-24 22:07 ` Dave Chinner
2020-01-24 23:12 ` Christoph Hellwig [this message]
2020-01-26 2:43 ` Christoph Hellwig
2020-01-24 5:20 ` [PATCH 11/12] xfs: remove unnecessary null pointer checks from _read_agf callers Darrick J. Wong
2020-01-24 5:20 ` [PATCH 12/12] xfs: fix xfs_buf_ioerror_alert location reporting Darrick J. Wong
2020-01-24 23:12 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2020-01-23 7:41 [PATCH v4 00/12] xfs: make buffer functions return error codes Darrick J. Wong
2020-01-23 7:42 ` [PATCH 10/12] xfs: make xfs_*read_agf return EAGAIN to ALLOC_FLAG_TRYLOCK callers Darrick J. Wong
2020-01-24 2:00 ` Dave Chinner
2020-01-24 4:47 ` 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=20200124231207.GD20014@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@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;
as well as URLs for NNTP newsgroup(s).