From: Gabriel Krisman Bertazi <gabriel@krisman.be>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: brauner@kernel.org, hch@lst.de, jack@suse.cz,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, amir73il@gmail.com
Subject: Re: [PATCH 6/6] ext4: convert to new fserror helpers
Date: Mon, 12 Jan 2026 19:56:09 -0500 [thread overview]
Message-ID: <87zf6i2uvq.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <176826402693.3490369.5875002879192895558.stgit@frogsfrogsfrogs> (Darrick J. Wong's message of "Mon, 12 Jan 2026 16:32:27 -0800")
"Darrick J. Wong" <djwong@kernel.org> writes:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Use the new fserror functions to report metadata errors to fsnotify.
> Note that ext4 inconsistently passes around negative and positive error
> numbers all over the codebase, so we force them all to negative for
> consistency in what we report to fserror, and fserror ensures that only
> positive error numbers are passed to fanotify, per the fanotify(7)
> manpage.
>
> Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Jan Kara <jack@suse.cz>
> ---
> fs/ext4/ioctl.c | 2 ++
> fs/ext4/super.c | 13 +++++++++----
> 2 files changed, 11 insertions(+), 4 deletions(-)
>
>
> diff --git a/fs/ext4/ioctl.c b/fs/ext4/ioctl.c
> index 7ce0fc40aec2fb..ea26cd03d3ce28 100644
> --- a/fs/ext4/ioctl.c
> +++ b/fs/ext4/ioctl.c
> @@ -26,6 +26,7 @@
> #include <linux/fsmap.h>
> #include "fsmap.h"
> #include <trace/events/ext4.h>
> +#include <linux/fserror.h>
>
> typedef void ext4_update_sb_callback(struct ext4_sb_info *sbi,
> struct ext4_super_block *es,
> @@ -844,6 +845,7 @@ int ext4_force_shutdown(struct super_block *sb, u32 flags)
> return -EINVAL;
> }
> clear_opt(sb, DISCARD);
> + fserror_report_shutdown(sb, GFP_KERNEL);
> return 0;
> }
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 87205660c5d026..a6241ffb8639c3 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -48,6 +48,7 @@
> #include <linux/fsnotify.h>
> #include <linux/fs_context.h>
> #include <linux/fs_parser.h>
> +#include <linux/fserror.h>
>
> #include "ext4.h"
> #include "ext4_extents.h" /* Needed for trace points definition */
> @@ -824,7 +825,8 @@ void __ext4_error(struct super_block *sb, const char *function,
> sb->s_id, function, line, current->comm, &vaf);
> va_end(args);
> }
> - fsnotify_sb_error(sb, NULL, error ? error : EFSCORRUPTED);
> + fserror_report_metadata(sb, error ? -abs(error) : -EFSCORRUPTED,
> + GFP_ATOMIC);
>
> ext4_handle_error(sb, force_ro, error, 0, block, function, line);
> }
> @@ -856,7 +858,9 @@ void __ext4_error_inode(struct inode *inode, const char *function,
> current->comm, &vaf);
> va_end(args);
> }
> - fsnotify_sb_error(inode->i_sb, inode, error ? error : EFSCORRUPTED);
> + fserror_report_file_metadata(inode,
> + error ? -abs(error) : -EFSCORRUPTED,
> + GFP_ATOMIC);
>
> ext4_handle_error(inode->i_sb, false, error, inode->i_ino, block,
> function, line);
> @@ -896,7 +900,7 @@ void __ext4_error_file(struct file *file, const char *function,
> current->comm, path, &vaf);
> va_end(args);
> }
> - fsnotify_sb_error(inode->i_sb, inode, EFSCORRUPTED);
> + fserror_report_file_metadata(inode, -EFSCORRUPTED, GFP_ATOMIC);
>
> ext4_handle_error(inode->i_sb, false, EFSCORRUPTED, inode->i_ino, block,
> function, line);
> @@ -965,7 +969,8 @@ void __ext4_std_error(struct super_block *sb, const char *function,
> printk(KERN_CRIT "EXT4-fs error (device %s) in %s:%d: %s\n",
> sb->s_id, function, line, errstr);
> }
> - fsnotify_sb_error(sb, NULL, errno ? errno : EFSCORRUPTED);
> + fserror_report_metadata(sb, errno ? -abs(errno) : -EFSCORRUPTED,
> + GFP_ATOMIC);
>
> ext4_handle_error(sb, false, -errno, 0, 0, function, line);
> }
>
Perhaps also delete fsnotify_sb_error after this patch since it is now
implemented by fserror_worker and, if I follow correctly, we don't want
it to be called without the shutdown protection mechanism.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2026-01-13 0:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 0:31 [PATCHSET v5] fs: generic file IO error reporting Darrick J. Wong
2026-01-13 0:31 ` [PATCH 1/6] uapi: promote EFSCORRUPTED and EUCLEAN to errno.h Darrick J. Wong
2026-01-13 0:31 ` [PATCH 2/6] fs: report filesystem and file I/O errors to fsnotify Darrick J. Wong
2026-01-13 8:24 ` Christoph Hellwig
2026-01-13 0:31 ` [PATCH 3/6] iomap: report file I/O errors to the VFS Darrick J. Wong
2026-01-13 0:31 ` [PATCH 4/6] xfs: report fs metadata errors via fsnotify Darrick J. Wong
2026-01-13 0:32 ` [PATCH 5/6] xfs: translate fsdax media errors into file "data lost" errors when convenient Darrick J. Wong
2026-01-13 0:32 ` [PATCH 6/6] ext4: convert to new fserror helpers Darrick J. Wong
2026-01-13 0:56 ` Gabriel Krisman Bertazi [this message]
2026-01-13 1:26 ` Darrick J. Wong
2026-01-15 15:29 ` Theodore Tso
2026-01-13 8:58 ` [PATCHSET v5] fs: generic file IO error reporting Christian Brauner
-- strict thread matches above, loose matches on Subject: below --
2025-12-18 2:02 [PATCHSET V4 1/2] " Darrick J. Wong
2025-12-18 2:04 ` [PATCH 6/6] ext4: convert to new fserror helpers Darrick J. Wong
2025-12-18 5:23 ` Christoph Hellwig
2025-12-22 15:34 ` Jan Kara
2026-01-06 17:30 ` Darrick J. Wong
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=87zf6i2uvq.fsf@mailhost.krisman.be \
--to=gabriel@krisman.be \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.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