[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260112185042.GB15532@frogsfrogsfrogs>
Date: Mon, 12 Jan 2026 10:50:42 -0800
From: "Darrick J. Wong" <djwong@...nel.org>
To: Christian Brauner <brauner@...nel.org>
Cc: Christoph Hellwig <hch@...radead.org>, linux-ext4@...r.kernel.org,
jack@...e.cz, linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, gabriel@...sman.be,
amir73il@...il.com
Subject: Re: [PATCH 2/6] fs: report filesystem and file I/O errors to fsnotify
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
Powered by blists - more mailing lists