From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/6] xfs: improve the xfs_buf_ioend_fail calling convention
Date: Wed, 24 Jun 2026 09:42:06 +0200 [thread overview]
Message-ID: <20260624074206.GA12969@lst.de> (raw)
In-Reply-To: <ajkxAU-VxjRrHVS0@nidhogg.toxiclabs.cc>
On Mon, Jun 22, 2026 at 02:59:05PM +0200, Carlos Maiolino wrote:
> On Mon, Jun 22, 2026 at 09:30:02AM +0200, Christoph Hellwig wrote:
> > Move setting the ASYNC flag into xfs_buf_ioend_fail_async, assert that
> Is this a typo? I can't find this
> definition anywhere and the code also
> moves this into xfs_buf_ioend_fail(),
> not into a _async variation.
Yeah, this could use a little update.
next prev parent reply other threads:[~2026-06-24 7:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 7:29 xfs_buf_submit error handling fix Christoph Hellwig
2026-06-22 7:30 ` [PATCH 1/6] xfs: open code xfs_buf_ioend_fail in xfs_buf_submit Christoph Hellwig
2026-06-22 12:39 ` Carlos Maiolino
2026-06-22 7:30 ` [PATCH 2/6] xfs: also mark the buffer stale on verifier failure " Christoph Hellwig
2026-06-22 12:42 ` Carlos Maiolino
2026-06-22 7:30 ` [PATCH 3/6] xfs: improve the xfs_buf_ioend_fail calling convention Christoph Hellwig
2026-06-22 12:59 ` Carlos Maiolino
2026-06-24 7:42 ` Christoph Hellwig [this message]
2026-06-24 8:26 ` Carlos Maiolino
2026-06-24 13:44 ` Christoph Hellwig
2026-06-22 7:30 ` [PATCH 4/6] xfs: remove xfs_buf_ioend Christoph Hellwig
2026-06-22 13:17 ` Carlos Maiolino
2026-06-22 7:30 ` [PATCH 5/6] xfs: fix handling of synchronous errors in xfs_buf_submit Christoph Hellwig
2026-06-22 13:34 ` Carlos Maiolino
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=20260624074206.GA12969@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--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