From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL 05/12 for v7.0] vfs fserror
Date: Fri, 6 Feb 2026 17:50:01 +0100 [thread overview]
Message-ID: <20260206-vfs-fserror-v70-7d1adc65b98d@brauner> (raw)
In-Reply-To: <20260206-vfs-v70-7df0b750d594@brauner>
Hey Linus,
/* Summary */
This contains the changes to support generif I/O error reporting.
Filesystems currently have no standard mechanism for reporting metadata
corruption and file I/O errors to userspace via fsnotify. Each
filesystem (xfs, ext4, erofs, f2fs, etc.) privately defines
EFSCORRUPTED, and error reporting to fanotify is inconsistent or absent
entirely.
This series introduces a generic fserror infrastructure built around
struct super_block that gives filesystems a standard way to queue
metadata and file I/O error reports for delivery to fsnotify. Errors
are queued via mempools and queue_work to avoid holding filesystem locks
in the notification path; unmount waits for pending events to drain. A
new super_operations::report_error callback lets filesystem drivers
respond to file I/O errors themselves (to be used by an upcoming XFS
self-healing patchset).
On the uapi side, EFSCORRUPTED and EUCLEAN are promoted from private
per-filesystem definitions to canonical errno.h values across all
architectures.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3+b1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-7.0-rc1.fserror
for you to fetch changes up to 347b7042fb26beaae1ea46d0f6c47251fb52985f:
Merge patch series "fs: generic file IO error reporting" (2026-01-13 09:58:07 +0100)
----------------------------------------------------------------
vfs-7.0-rc1.fserror
Please consider pulling these changes from the signed vfs-7.0-rc1.fserror tag.
Thanks!
Christian
----------------------------------------------------------------
Christian Brauner (1):
Merge patch series "fs: generic file IO error reporting"
Darrick J. Wong (6):
uapi: promote EFSCORRUPTED and EUCLEAN to errno.h
fs: report filesystem and file I/O errors to fsnotify
iomap: report file I/O errors to the VFS
xfs: report fs metadata errors via fsnotify
xfs: translate fsdax media errors into file "data lost" errors when convenient
ext4: convert to new fserror helpers
arch/alpha/include/uapi/asm/errno.h | 2 +
arch/mips/include/uapi/asm/errno.h | 2 +
arch/parisc/include/uapi/asm/errno.h | 2 +
arch/sparc/include/uapi/asm/errno.h | 2 +
fs/Makefile | 2 +-
fs/erofs/internal.h | 2 -
fs/ext2/ext2.h | 1 -
fs/ext4/ext4.h | 3 -
fs/ext4/ioctl.c | 2 +
fs/ext4/super.c | 13 +-
fs/f2fs/f2fs.h | 3 -
fs/fserror.c | 194 +++++++++++++++++++++++++++++
fs/iomap/buffered-io.c | 23 +++-
fs/iomap/direct-io.c | 12 ++
fs/iomap/ioend.c | 6 +
fs/minix/minix.h | 2 -
fs/super.c | 3 +
fs/udf/udf_sb.h | 2 -
fs/xfs/xfs_fsops.c | 4 +
fs/xfs/xfs_health.c | 14 +++
fs/xfs/xfs_linux.h | 2 -
fs/xfs/xfs_notify_failure.c | 4 +
include/linux/fs/super_types.h | 7 ++
include/linux/fserror.h | 75 +++++++++++
include/linux/jbd2.h | 3 -
include/uapi/asm-generic/errno.h | 2 +
tools/arch/alpha/include/uapi/asm/errno.h | 2 +
tools/arch/mips/include/uapi/asm/errno.h | 2 +
tools/arch/parisc/include/uapi/asm/errno.h | 2 +
tools/arch/sparc/include/uapi/asm/errno.h | 2 +
tools/include/uapi/asm-generic/errno.h | 2 +
31 files changed, 373 insertions(+), 24 deletions(-)
create mode 100644 fs/fserror.c
create mode 100644 include/linux/fserror.h
next prev parent reply other threads:[~2026-02-06 16:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 16:49 [GIT PULL 00/12 for v7.0] v7.0 Christian Brauner
2026-02-06 16:49 ` [GIT PULL 01/12 for v7.0] vfs rust Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-06 16:49 ` [GIT PULL 02/12 for v7.0] vfs initrd Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-06 16:49 ` [GIT PULL 03/12 for v7.0] vfs nonblocking_timestamps Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-06 16:50 ` [GIT PULL 04/12 for v7.0] vfs leases Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-06 16:50 ` Christian Brauner [this message]
2026-02-10 0:50 ` [GIT PULL 05/12 for v7.0] vfs fserror pr-tracker-bot
2026-02-06 16:50 ` [GIT PULL 06/12 for v7.0] vfs btrfs Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-06 16:50 ` [GIT PULL 07/12 for v7.0] vfs minix Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-06 16:50 ` [GIT PULL 08/12 for v7.0] vfs nullfs Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-06 16:50 ` [GIT PULL 09/12 for v7.0] vfs atomic_open Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-06 16:50 ` [GIT PULL 10/12 for v7.0] vfs namespace Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-06 16:50 ` [GIT PULL 11/12 for v7.0] vfs iomap Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-06 16:50 ` [GIT PULL 12/12 for v7.0] vfs misc Christian Brauner
2026-02-07 5:11 ` Nathan Chancellor
2026-02-09 9:31 ` Christian Brauner
2026-02-10 0:50 ` pr-tracker-bot
2026-02-16 12:29 ` [GIT PULL 13/12 for v7.0] kernel misc Christian Brauner
2026-02-16 22:11 ` pr-tracker-bot
2026-02-16 12:55 ` [GIT PULL 14/12 for v7.0] vfs misc 2 Christian Brauner
2026-02-16 22:11 ` pr-tracker-bot
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=20260206-vfs-fserror-v70-7d1adc65b98d@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®