Re: fanotify - overall design before I start sending patches

[Alan Cox]

> > We are taking about the kind of fanotify client that says: No you cannot
> > open/read/write/mmap/etc.. this file until I say you can, right?
> 
> Yes and no, it would be more accurate to say "this open takes long while we do 
> something else in the background".

There are two or three ways to handle this

1.	Block the open until the daemon dies or responds
2.	Have a timeout (which would need to be connection configurable)
3.	Require the daemon responds with "in progress" now and then.

For a superuser managed service its no different to an NFS mount which
can go wonky so the only real question is what should fanotify allow non
privileged users to do. The answer would appear anyway to be: not use
this aspect of such a facility.

For the superuser case the fact the daemon can be killed thus releasing
anything stuff is analogous to umount -f of a stuck NFS mount which seems
perfectly good for NFS.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/