From: "Darrick J. Wong" <djwong@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-ext4@vger.kernel.org, jack@suse.cz,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
gabriel@krisman.be, amir73il@gmail.com
Subject: Re: [PATCH 2/6] fs: report filesystem and file I/O errors to fsnotify
Date: Mon, 12 Jan 2026 10:50:42 -0800 [thread overview]
Message-ID: <20260112185042.GB15532@frogsfrogsfrogs> (raw)
In-Reply-To: <20260112-anpassen-konglomerat-fce55d3de81b@brauner>
On Mon, Jan 12, 2026 at 02:17:14PM +0100, Christian Brauner wrote:
> On Tue, Jan 06, 2026 at 08:42:30AM -0800, Darrick J. Wong wrote:
> > On Wed, Dec 24, 2025 at 01:29:21PM +0100, Christian Brauner wrote:
> > > > Nope. Fixed.
> > >
> > > I've pulled this from the provided branch which already contains the
> > > mentioned fixes. It now lives in vfs-7.0.fserror. As an aside, the
> > > numbering for this patch series was very odd which tripped b4 so I
> > > applied it with manual massaging. Let me know if there are any issues.
> >
> > Thank you! But, uh... do you want me to fix the things that hch and jan
> > mentioned? Or have you already fixed them? I don't see a
> > vfs-7.0.fserror branch on the vfs tree[1]...
> >
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git/refs/heads
>
> Before Christmas and the new year I didn't push anything out so we don't
> end up in a situation where -next is broken but half the people are
> still on vacation or are busy catching up.
>
> I'm back now. Please just send a version with the fixes now.
Ok, thanks for the update. I'll send the latest version to -fsdevel.
--D
next prev parent reply other threads:[~2026-01-12 18:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 2:02 [PATCHSET V4 1/2] fs: generic file IO error reporting Darrick J. Wong
2025-12-18 2:02 ` [PATCH 1/6] uapi: promote EFSCORRUPTED and EUCLEAN to errno.h Darrick J. Wong
2025-12-18 5:17 ` Christoph Hellwig
2025-12-18 11:04 ` Alejandro Colomar
2025-12-18 18:45 ` Darrick J. Wong
2025-12-18 9:33 ` Gao Xiang
2025-12-22 15:01 ` Jan Kara
2025-12-18 2:03 ` [PATCH 2/6] fs: report filesystem and file I/O errors to fsnotify Darrick J. Wong
2025-12-18 5:21 ` Christoph Hellwig
2025-12-18 18:44 ` Darrick J. Wong
2025-12-24 12:29 ` Christian Brauner
2026-01-06 16:42 ` Darrick J. Wong
2026-01-12 13:17 ` Christian Brauner
2026-01-12 18:50 ` Darrick J. Wong [this message]
2025-12-18 23:32 ` [PATCH V4.1 " Darrick J. Wong
2025-12-22 15:36 ` [PATCH " Jan Kara
2026-01-06 17:35 ` Darrick J. Wong
2025-12-18 2:03 ` [PATCH 3/6] iomap: report file I/O errors to the VFS Darrick J. Wong
2025-12-18 5:22 ` Christoph Hellwig
2025-12-22 15:30 ` Jan Kara
2025-12-18 2:03 ` [PATCH 4/6] xfs: report fs metadata errors via fsnotify Darrick J. Wong
2025-12-18 5:22 ` Christoph Hellwig
2025-12-18 2:03 ` [PATCH 5/6] xfs: translate fsdax media errors into file "data lost" errors when convenient Darrick J. Wong
2025-12-18 5:23 ` Christoph Hellwig
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
2026-01-06 23:33 ` [PATCH 7/6] fs: improve comment in fserror_alloc_event Darrick J. Wong
2026-01-07 9:19 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2026-01-13 0:31 [PATCHSET v5] fs: generic file IO error reporting 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
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=20260112185042.GB15532@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=gabriel@krisman.be \
--cc=hch@infradead.org \
--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