All of lore.kernel.org
 help / color / mirror / Atom feed
From: cem@kernel.org
To: cem@kernel.org
Cc: djwong@kernel.org, hchc@last.de, sandeen@sandeen.net,
	linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/3] Enable xfs error reporting to print out error codes
Date: Mon, 14 Sep 2026 13:57:38 +0200	[thread overview]
Message-ID: <20260914115746.82122-1-cem@kernel.org> (raw)

From: Carlos Maiolino <cem@kernel.org>

Hi,

this is the V2 of this series addressing the comments from the previous
version. Details are in each individual patch, but the main change:

I removed the errname() call from patch 1. Turns out it would make
things more complicated as we'd need to not only check if
xfs_error_report() receives an error, but also if errname() returned a
non-NULL value. Having the error name was a nice to have thing, but
printing only the error number make things simpler.

Also hch already cleaned the extern modifiers from the prototypes so I
removed it from here.

Carlos Maiolino (3):
  xfs: add xfs_error_report the ability to display an error code
  xfs: enable xfs_trans_cancel() to report and error code
  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         |  6 +++++-
 8 files changed, 37 insertions(+), 19 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-09-14 11:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 11:57 cem [this message]
2026-09-14 11:57 ` [PATCH v2 1/3] xfs: add xfs_error_report the ability to display an error code cem
2026-09-14 14:42   ` Darrick J. Wong
2026-09-14 15:00     ` Carlos Maiolino
2026-09-14 15:08       ` Darrick J. Wong
2026-09-17 10:22         ` Carlos Maiolino
2026-09-14 11:57 ` [PATCH v2 2/3] xfs: enable xfs_trans_cancel() to report and " cem
2026-09-14 14:38   ` Darrick J. Wong
2026-09-14 11:57 ` [PATCH v2 3/3] xfs: make xfs_iomap_write_direct() report an error to xfs_trans_cancel cem

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=20260914115746.82122-1-cem@kernel.org \
    --to=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hchc@last.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.