Re: PROBLEM: FUSE_NOTIFY_INVAL_ENTRY leaves stale negative dentry after c9ba789dad15

On Wed, 10 Jun 2026, Miklos Szeredi wrote:
> On Thu, 4 Jun 2026 at 15:59, Miklos Szeredi <[email protected]> wrote:
> 
> > Okay, so this is about making VFS more scalable?  Can't we just leave
> > filesystem code alone in that case?
> 
> Unless there are strong objections I'm going to revert commit
> cab012375122 ("fuse: fix conversion of fuse_reverse_inval_entry() to
> start_removing()") and revert the fuse part of commit c9ba789dad15
> ("VFS: introduce start_creating_noperm() and
> start_removing_noperm()").

I think that is a good idea at this stage.  Hopefully I'll come back and
revisit this in another cycle.

Thanks,
NeilBrown


> 
> Thanks,
> Miklos
>