From: Carlos Maiolino <cem@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: hch@lst.de, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/3] xfs: add xfs_error_report the ability to display an error code
Date: Thu, 10 Sep 2026 11:24:24 +0200 [thread overview]
Message-ID: <aqJ1pZhNeTyvALhl@andromeda.toxiclabs.cc> (raw)
In-Reply-To: <20260908151635.GE2619314@frogsfrogsfrogs>
On Tue, Sep 08, 2026 at 08:16:35AM -0700, Darrick J. Wong wrote:
> On Tue, Sep 08, 2026 at 04:54:14PM +0200, cem@kernel.org wrote:
> > From: Carlos Maiolino <cem@kernel.org>
> >
> > Users could opt to request an error code to be printed now.
> > This relies on errname() and CONFIG_SYMBOLIC_NAME without requiring it
> > to be enabled.
> > Report 'unkown error' If CONFIG_SYMBOLIC_NAME is not enabled or the
> > user passes 0 as an error.
> >
> > Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> > ---
> > fs/xfs/xfs_error.c | 13 ++++++++++---
> > fs/xfs/xfs_error.h | 10 +++++-----
> > fs/xfs/xfs_exchmaps_item.c | 9 ++++++---
> > fs/xfs/xfs_inode_item.c | 3 ++-
> > fs/xfs/xfs_log_recover.c | 3 ++-
> > fs/xfs/xfs_trans.c | 2 +-
> > 6 files changed, 26 insertions(+), 14 deletions(-)
> >
> > diff --git a/fs/xfs/xfs_error.c b/fs/xfs/xfs_error.c
> > index dbd87e137694..3177ec58bb2e 100644
> > --- a/fs/xfs/xfs_error.c
> > +++ b/fs/xfs/xfs_error.c
> > @@ -14,6 +14,7 @@
> > #include "xfs_error.h"
> > #include "xfs_sysfs.h"
> > #include "xfs_inode.h"
> > +#include <linux/errname.h>
> >
> > #ifdef DEBUG
> >
> > @@ -377,15 +378,21 @@ void
> > xfs_error_report(
> > const char *tag,
> > int level,
> > + int error,
> > struct xfs_mount *mp,
> > const char *filename,
> > int linenum,
> > xfs_failaddr_t failaddr)
> > {
> > + const char *err_str = errname(error);
> > +
> > + if (!err_str)
> > + err_str = "unknown error";
>
> Should it just snprintf the error number to a buffer?
I thought about that and also about using num_to_str() to print out the
error number *if* the ERRNAME config is disabled. I just thought it
wasn't worth handling an extra buffer here giving ERRNAME is enabled on
most major distros AFAICT.
I quick chat with Eric too and he suggested "unknown error" might be
confusing and perhaps replace the above with a blank string like:
err_str = "";
My whole point though in doing this way by not using a snprintf() and
num_to_str() is I believe it would be an overkill for this and opted to
KISS :)
> > +
> > if (level <= xfs_error_level) {
> > xfs_alert_tag(mp, XFS_PTAG_ERROR_REPORT,
> > - "Internal error %s at line %d of file %s. Caller %pS",
> > - tag, linenum, filename, failaddr);
> > + "Internal error %s (%s) at line %d of file %s. Caller %pS",
> > + tag, err_str, linenum, filename, failaddr);
> >
> > xfs_stack_trace();
> > }
> > @@ -404,7 +411,7 @@ xfs_corruption_error(
> > {
> > if (buf && level <= xfs_error_level)
> > xfs_hex_dump(buf, bufsize);
> > - xfs_error_report(tag, level, mp, filename, linenum, failaddr);
> > + xfs_error_report(tag, level, 0, mp, filename, linenum, failaddr);
>
> Shouldn't this be -EFSCORRUPTED too?
Indeed, I didn't want to change any 'implicit' error handling in this
patch specifically. I was hoping to do that in a future patch adding
errors where pertinent. But I have zero objection in changing this.
>
> --D
>
> > xfs_alert(mp, "Corruption detected. Unmount and run xfs_repair");
> > }
> >
> > diff --git a/fs/xfs/xfs_error.h b/fs/xfs/xfs_error.h
> > index 0b9c5ba8a598..f3b5564c2f4f 100644
> > --- a/fs/xfs/xfs_error.h
> > +++ b/fs/xfs/xfs_error.h
> > @@ -8,9 +8,9 @@
> >
> > struct xfs_mount;
> >
> > -extern void xfs_error_report(const char *tag, int level, struct xfs_mount *mp,
> > - const char *filename, int linenum,
> > - xfs_failaddr_t failaddr);
> > +void xfs_error_report(const char *tag, int level, int error,
> > + struct xfs_mount *mp, const char *filename,
> > + int linenum, xfs_failaddr_t failaddr);
> > extern void xfs_corruption_error(const char *tag, int level,
> > struct xfs_mount *mp, const void *buf, size_t bufsize,
> > const char *filename, int linenum,
> > @@ -25,8 +25,8 @@ extern void xfs_inode_verifier_error(struct xfs_inode *ip, int error,
> > const char *name, const void *buf, size_t bufsz,
> > xfs_failaddr_t failaddr);
> >
> > -#define XFS_ERROR_REPORT(e, lvl, mp) \
> > - xfs_error_report(e, lvl, mp, __FILE__, __LINE__, __return_address)
> > +#define XFS_ERROR_REPORT(e, lvl, error, mp) \
> > + xfs_error_report(e, lvl, error, mp, __FILE__, __LINE__, __return_address)
> > #define XFS_CORRUPTION_ERROR(e, lvl, mp, buf, bufsize) \
> > xfs_corruption_error(e, lvl, mp, buf, bufsize, \
> > __FILE__, __LINE__, __return_address)
> > diff --git a/fs/xfs/xfs_exchmaps_item.c b/fs/xfs/xfs_exchmaps_item.c
> > index 264a121c5e16..2cbc1b9aee43 100644
> > --- a/fs/xfs/xfs_exchmaps_item.c
> > +++ b/fs/xfs/xfs_exchmaps_item.c
> > @@ -559,13 +559,15 @@ xlog_recover_xmi_commit_pass2(
> >
> > len = sizeof(struct xfs_xmi_log_format);
> > if (item->ri_buf[0].i_len != len) {
> > - XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW, log->l_mp);
> > + XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW,
> > + -EFSCORRUPTED, log->l_mp);
> > return -EFSCORRUPTED;
> > }
> >
> > xmi_formatp = item->ri_buf[0].i_addr;
> > if (xmi_formatp->__pad != 0) {
> > - XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW, log->l_mp);
> > + XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW,
> > + -EFSCORRUPTED, log->l_mp);
> > return -EFSCORRUPTED;
> > }
> >
> > @@ -600,7 +602,8 @@ xlog_recover_xmd_commit_pass2(
> >
> > xmd_formatp = item->ri_buf[0].i_addr;
> > if (item->ri_buf[0].i_len != sizeof(struct xfs_xmd_log_format)) {
> > - XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW, log->l_mp);
> > + XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW,
> > + -EFSCORRUPTED, log->l_mp);
> > return -EFSCORRUPTED;
> > }
> >
> > diff --git a/fs/xfs/xfs_inode_item.c b/fs/xfs/xfs_inode_item.c
> > index c6cb0b6b9e46..c361e02110a0 100644
> > --- a/fs/xfs/xfs_inode_item.c
> > +++ b/fs/xfs/xfs_inode_item.c
> > @@ -1185,7 +1185,8 @@ xfs_inode_item_format_convert(
> > struct xfs_inode_log_format_32 *in_f32 = buf->i_addr;
> >
> > if (buf->i_len != sizeof(*in_f32)) {
> > - XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW, NULL);
> > + XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW,
> > + -EFSCORRUPTED, NULL);
> > return -EFSCORRUPTED;
> > }
> >
> > diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
> > index 2f76531842f8..b1979d00d2e3 100644
> > --- a/fs/xfs/xfs_log_recover.c
> > +++ b/fs/xfs/xfs_log_recover.c
> > @@ -2932,7 +2932,8 @@ xlog_recover_process(
> > * fatal log corruption failure.
> > */
> > if (xfs_has_crc(log->l_mp)) {
> > - XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW, log->l_mp);
> > + XFS_ERROR_REPORT(__func__, XFS_ERRLEVEL_LOW,
> > + -EFSCORRUPTED, log->l_mp);
> > return -EFSCORRUPTED;
> > }
> > }
> > diff --git a/fs/xfs/xfs_trans.c b/fs/xfs/xfs_trans.c
> > index c6657072361a..792a67a7ec28 100644
> > --- a/fs/xfs/xfs_trans.c
> > +++ b/fs/xfs/xfs_trans.c
> > @@ -999,7 +999,7 @@ xfs_trans_cancel(
> > * here.
> > */
> > if (dirty && !xfs_is_shutdown(mp)) {
> > - XFS_ERROR_REPORT("xfs_trans_cancel", XFS_ERRLEVEL_LOW, mp);
> > + XFS_ERROR_REPORT("xfs_trans_cancel", XFS_ERRLEVEL_LOW, 0, mp);
> > xfs_force_shutdown(mp, SHUTDOWN_CORRUPT_INCORE);
> > }
> > #ifdef DEBUG
> > --
> > 2.55.0
> >
> >
>
next prev parent reply other threads:[~2026-09-10 9:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 14:54 [PATCH 0/3] Enable xfs error reporting to print out error codes cem
2026-09-08 14:54 ` [PATCH 1/3] xfs: add xfs_error_report the ability to display an error code cem
2026-09-08 15:16 ` Darrick J. Wong
2026-09-10 9:24 ` Carlos Maiolino [this message]
2026-09-08 16:53 ` Eric Sandeen
2026-09-08 17:02 ` Darrick J. Wong
2026-09-08 20:40 ` Eric Sandeen
2026-09-10 9:33 ` Carlos Maiolino
2026-09-08 14:54 ` [PATCH 2/3] xfs: enable xfs_trans_cancel() to report and " cem
2026-09-08 15:27 ` Darrick J. Wong
2026-09-10 9:17 ` Carlos Maiolino
2026-09-08 14:54 ` [PATCH 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=aqJ1pZhNeTyvALhl@andromeda.toxiclabs.cc \
--to=cem@kernel.org \
--cc=djwong@kernel.org \
--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