[fuse-devel] kernel api 7.1

[Valient G. <vg...@po...>]

Hi Miklos,

I haven't tested your new locking code yet, but I was examining the latest 
changes from the kernel 7.1 bump.  Looks like the only change is 
fuse_forget_in.version field changed to .nlookup, right?

libfuse subtracts off the kernel-supplied .nlookup value from its own internal 
value to decide if it can really apply the forget.  Makes sense, and seems 
easier to ensure safety vs. the .version mechanism...

But as I was following around the forget logic in the kernel code, I'm a bit 
confused about fuse_inode.forget_req.  In fuse_clear_inode, fi->forget_req is 
set to NULL.  That structure was allocated by fuse_request_alloc(), right?  
So how does it get freed?

thanks,
Valient