[fuse-devel] Fwd: How does fuse_lowlevel_notify_inval_inode work?

[Stef B. <st...@gm...>]

---------- Forwarded message ----------
From: Stef Bon <st...@gm...>
Date: 2014-03-17 17:51 GMT+01:00
Subject: Re: [fuse-devel] How does fuse_lowlevel_notify_inval_inode work?
To: Brian Foster <bf...@re...>


Hi Brian,

I've seen that in the kernel. But then I still do not understand. What
values do I have to use to for example invalidate the uid of an inode?

I'm working on enabling fsnotify for fuse. I've patched the kernel, and libfuse,
so my simple overlayfs receives a message (with new opcode FUSE_FSNOTIFY).

It does not work perfect yet, but my fuse fs simple overlayfs receives
a message when a watch has been set on an inode.
The simpleoverlayfs sets a watch on it's backend, in this case it's
simple because
that is the same system. I use inotify for that. When a change is
detected, simpleoverlays reacts on the changes. The only thing what
does not work yet is push the right changes to the kernel. So that's
why I ask. (note: I'm talking about the attributes for now, and a
delete and a add of an entry

it looks like:

notify_inval_inode is for changing attributes of an inode
notify_delete is for deleting an entry

and when an entry is new? There is no call yet.


Stef