Messages in this thread | | | From | "Paul Rolland" <> | Subject | Re: [RFC,PATCH] dnotify: enhance or replace? | Date | Wed, 24 Mar 2004 21:00:01 +0100 |
| |
Hello,
> could be done. Inode numbers are not unique, but is there any > way to get > a unique identifier on a file without using an open file? I have come I wonder if adding to the inode number something like the device id is not enough to create some "unique key"...
> up with a few ideas.. I don't think they are very good, but here is > goes, > > - When user passes fd to kernel to watch, the kernel takes over this > fd, making it invalid in user space ( I know this is a > terrible hack) > then when a volume is unmounted, the kernel can walk the list of > open fd's using for notifacation and close them, before > attempting to > unmount. No, this is bad, because it would require to use dedicated fd for dnotify. If I open a file/directory, give it to dnotify, I don't want to re-open it to use it, read it, or anything else...
> - The user passes a path to the kernel, the kernel does some work so > that it can track anything to do with that path, and again when > an unmount is called the kernel cleans up anything used for > notification. That sounds much better to me...
Regards, Paul
Paul Rolland, rol(at)as2917.net ex-AS2917 Network administrator and Peering Coordinator
--
Please no HTML, I'm not a browser - Pas d'HTML, je ne suis pas un navigateur
"Some people dream of success... while others wake up and work hard at it"
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |