From: cem@kernel.org
To: cem@kernel.org
Cc: linux-xfs@vger.kernel.org, hch@lst.de, djwong@kernel.org,
sandeen@sandeen.net
Subject: [PATCH v4 0/3] Enable xfs error reporting to print out error codes
Date: Thu, 24 Sep 2026 17:16:27 +0200 [thread overview]
Message-ID: <20260924151638.38535-1-cem@kernel.org> (raw)
From: Carlos Maiolino <cem@kernel.org>
This is the new version of the error code printing series.
The only modification here is on patch 2 which replaces the macros by
an inline function suggested by hch.
Darrick, I removed your RwB from patch 2 giving the way it implements
things now are considerable different
Carlos Maiolino (3):
xfs: add xfs_error_report the ability to display an error code
xfs: introduce xfs_trans_cancel_error()
xfs: make xfs_iomap_write_direct() report an error to xfs_trans_cancel
fs/xfs/xfs_error.c | 16 +++++++++++-----
fs/xfs/xfs_error.h | 9 +++++----
fs/xfs/xfs_exchmaps_item.c | 9 ++++++---
fs/xfs/xfs_inode_item.c | 3 ++-
fs/xfs/xfs_iomap.c | 2 +-
fs/xfs/xfs_log_recover.c | 3 ++-
fs/xfs/xfs_trans.c | 8 +++++---
fs/xfs/xfs_trans.h | 9 ++++++++-
8 files changed, 40 insertions(+), 19 deletions(-)
--
2.55.0
next reply other threads:[~2026-09-24 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 15:16 cem [this message]
2026-09-24 15:16 ` [PATCH v4 1/3] xfs: add xfs_error_report the ability to display an error code cem
2026-09-24 15:16 ` [PATCH v4 2/3] xfs: introduce xfs_trans_cancel_error() cem
2026-09-24 18:57 ` Darrick J. Wong
2026-09-25 4:46 ` Christoph Hellwig
2026-09-24 15:16 ` [PATCH v4 3/3] xfs: make xfs_iomap_write_direct() report an error to xfs_trans_cancel cem
2026-10-05 18:06 ` [PATCH v4 0/3] Enable xfs error reporting to print out error codes Carlos Maiolino
2026-10-08 13:32 ` 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=20260924151638.38535-1-cem@kernel.org \
--to=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.