> On Sep 2, 2025, at 7:41 AM, Miklos Szeredi <mszeredi@xxxxxxxxxx> wrote: > > External email: Use caution opening links or attachments > > > Some fuse servers need to prune their caches, which can only be done if the > kernel's own dentry/inode caches are pruned first to avoid dangling > references. > > Add FUSE_NOTIFY_PRUNE, which takes an array of node ID's to try and get rid > of. Inodes with active references are skipped. > > A similar functionality is already provided by FUSE_NOTIFY_INVAL_ENTRY with > the FUSE_EXPIRE_ONLY flag. Differences in the interface are > > FUSE_NOTIFY_INVAL_ENTRY: > > - can only prune one dentry > > - dentry is determined by parent ID and name > > - if inode has multiple aliases (cached hard links), then they would have > to be invalidated individually to be able to get rid of the inode > > FUSE_NOTIFY_PRUNE: > > - can prune multiple inodes > > - inodes determined by their node ID > > - aliases are taken care of automatically > > Signed-off-by: Miklos Szeredi <mszeredi@xxxxxxxxxx> Thanks Miklos, this looks great. I’ll give this a spin in our virtio-fs FUSE device. <snip>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
