From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org, Carlos Maiolino <cmaiolino@redhat.com>
Subject: Re: [PATCH 6/6] xfs: simplify __xfs_buf_ioend
Date: Thu, 25 Jun 2026 11:30:02 -0700 [thread overview]
Message-ID: <20260625183002.GK6078@frogsfrogsfrogs> (raw)
In-Reply-To: <20260625135849.2494779-7-hch@lst.de>
On Thu, Jun 25, 2026 at 03:58:36PM +0200, Christoph Hellwig wrote:
> __xfs_buf_ioend can only resubmit the buffer for asynchronous
> writes, which means the retry handling xfs_buf_iowait is not needed.
>
> Because of this can stop returning a value from __xfs_buf_ioend and
> just release the buffer for async I/O that does not require retries.
>
> Also drop the __-prefix now that the semantics are straight forward.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
This makes sense to me -- only async writes (e.g. logged buffers written
by the ail) get to go through the write retry mechanism; the synchronous
writers are either regular threads and can report errors, or they're
dquot/inode items and a cluster flush just marks the log item as failed.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_buf.c | 51 ++++++++++++++++++++++++------------------------
> 1 file changed, 26 insertions(+), 25 deletions(-)
>
> diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
> index 83549573e2cc..f8511c11e017 100644
> --- a/fs/xfs/xfs_buf.c
> +++ b/fs/xfs/xfs_buf.c
> @@ -1098,11 +1098,17 @@ xfs_buf_ioend_handle_error(
> return false;
> }
>
> -/* returns false if the caller needs to resubmit the I/O, else true */
> -static bool
> -__xfs_buf_ioend(
> +/*
> + * Complete a buffer read or write.
> + *
> + * Releases the buffer if the I/O was asynchronous.
> + */
> +static void
> +xfs_buf_ioend(
> struct xfs_buf *bp)
> {
> + bool async = bp->b_flags & XBF_ASYNC;
> +
> trace_xfs_buf_iodone(bp, _RET_IP_);
>
> if (bp->b_flags & XBF_READ) {
> @@ -1116,14 +1122,16 @@ __xfs_buf_ioend(
> if (bp->b_flags & XBF_READ_AHEAD)
> percpu_counter_dec(&bp->b_target->bt_readahead_count);
> } else {
> - if (!bp->b_error) {
> + if (unlikely(bp->b_error)) {
> + if (xfs_buf_ioend_handle_error(bp)) {
> + ASSERT(async);
> + return;
> + }
> + } else {
> bp->b_flags &= ~XBF_WRITE_FAIL;
> bp->b_flags |= XBF_DONE;
> }
>
> - if (unlikely(bp->b_error) && xfs_buf_ioend_handle_error(bp))
> - return false;
> -
> /* clear the retry state */
> bp->b_last_error = 0;
> bp->b_retries = 0;
> @@ -1143,18 +1151,15 @@ __xfs_buf_ioend(
>
> bp->b_flags &= ~(XBF_READ | XBF_WRITE | XBF_READ_AHEAD |
> _XBF_LOGRECOVERY);
> - return true;
> + if (async)
> + xfs_buf_relse(bp);
> }
>
> static void
> xfs_buf_ioend_work(
> struct work_struct *work)
> {
> - struct xfs_buf *bp =
> - container_of(work, struct xfs_buf, b_ioend_work);
> -
> - if (__xfs_buf_ioend(bp))
> - xfs_buf_relse(bp);
> + xfs_buf_ioend(container_of(work, struct xfs_buf, b_ioend_work));
> }
>
> void
> @@ -1195,8 +1200,7 @@ xfs_buf_fail(
> bp->b_flags &= ~XBF_DONE;
> xfs_buf_stale(bp);
> xfs_buf_ioerror(bp, -EIO);
> - if (__xfs_buf_ioend(bp))
> - xfs_buf_relse(bp);
> + xfs_buf_ioend(bp);
> }
>
> int
> @@ -1305,12 +1309,11 @@ xfs_buf_iowait(
> {
> ASSERT(!(bp->b_flags & XBF_ASYNC));
>
> - do {
> - trace_xfs_buf_iowait(bp, _RET_IP_);
> - wait_for_completion(&bp->b_iowait);
> - trace_xfs_buf_iowait_done(bp, _RET_IP_);
> - } while (!__xfs_buf_ioend(bp));
> + trace_xfs_buf_iowait(bp, _RET_IP_);
> + wait_for_completion(&bp->b_iowait);
> + trace_xfs_buf_iowait_done(bp, _RET_IP_);
>
> + xfs_buf_ioend(bp);
> return bp->b_error;
> }
>
> @@ -1403,12 +1406,10 @@ xfs_buf_submit(
> bp->b_flags &= ~XBF_DONE;
> xfs_buf_stale(bp);
> end_io:
> - if (bp->b_flags & XBF_ASYNC) {
> - if (__xfs_buf_ioend(bp))
> - xfs_buf_relse(bp);
> - } else {
> + if (bp->b_flags & XBF_ASYNC)
> + xfs_buf_ioend(bp);
> + else
> complete(&bp->b_iowait);
> - }
> }
>
> /*
> --
> 2.53.0
>
>
next prev parent reply other threads:[~2026-06-25 18:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 13:58 xfs_buf_submit error handling fix v2 Christoph Hellwig
2026-06-25 13:58 ` [PATCH 1/6] xfs: open code xfs_buf_ioend_fail in xfs_buf_submit Christoph Hellwig
2026-06-25 13:58 ` [PATCH 2/6] xfs: also mark the buffer stale on verifier failure " Christoph Hellwig
2026-06-25 18:00 ` Darrick J. Wong
2026-06-26 4:35 ` Christoph Hellwig
2026-06-26 6:21 ` Darrick J. Wong
2026-06-26 6:23 ` Christoph Hellwig
2026-06-26 14:47 ` Darrick J. Wong
2026-06-25 13:58 ` [PATCH 3/6] xfs: improve the xfs_buf_ioend_fail calling convention Christoph Hellwig
2026-06-25 18:04 ` Darrick J. Wong
2026-06-25 13:58 ` [PATCH 4/6] xfs: remove xfs_buf_ioend Christoph Hellwig
2026-06-25 18:09 ` Darrick J. Wong
2026-06-25 13:58 ` [PATCH 5/6] xfs: fix handling of synchronous errors in xfs_buf_submit Christoph Hellwig
2026-06-25 18:13 ` Darrick J. Wong
2026-06-26 4:36 ` Christoph Hellwig
2026-06-25 13:58 ` [PATCH 6/6] xfs: simplify __xfs_buf_ioend Christoph Hellwig
2026-06-25 18:30 ` Darrick J. Wong [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-22 7:29 xfs_buf_submit error handling fix Christoph Hellwig
2026-06-22 7:30 ` [PATCH 6/6] xfs: simplify __xfs_buf_ioend Christoph Hellwig
2026-06-22 14:10 ` Carlos Maiolino
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=20260625183002.GK6078@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=cmaiolino@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