Re: [PATCH v5 3/4] fs: handle potential filesystems which use I_DONTCACHE and drop the lock in ->drop_inode

[Christian Brauner]

On Thu, Apr 09, 2026 at 04:55:52PM +0200, Mateusz Guzik wrote:
> On Thu, Apr 9, 2026 at 3:40 PM Christian Brauner <brauner@xxxxxxxxxx> wrote:
> >
> > On Wed, Apr 01, 2026 at 08:50:39PM +0200, Mateusz Guzik wrote:
> > > On Wed, Apr 1, 2026 at 7:45 PM Jan Kara <jack@xxxxxxx> wrote:
> > > >
> > > > On Tue 31-03-26 18:08:50, Mateusz Guzik wrote:
> > > > > f2fs and ntfs play games where they transitioning the refcount 0->1 and release
> > > >
> > > > I don't see ntfs providing .drop_inode at all in current Linu's kernel? The
> > > > f2fs case is indeed ugly and a gross hack. But I don't see easy way how to
> > > > fix that for now.
> > > >
> > >
> > > This was generated against next-20260327, then:
> >
> > Ideally don't develop against next... If you already know you're going
> > to do a bunch of work in an area. I can just assign you a branch to work
> > of off. Easier for everyone. Also makes the CI easier.
> 
> So what should stuff be generated against? fs-next? vfs.all?

Use vfs.all