Hi, I have been working on inotify a dnotify replacement. inotify is a char device that has two ioctls: INOTIFY_WATCH and INOTIFY_IGNORE Which expect an inode number and an inode device number. I know that on some file systems the inode number and inode device number are not guaranteed to be unique. This driver is only meant for file systems that have unique inode numbers. The two biggest complaints people have about dnotify are 1) dnotify delivers events using signals. 2) dnotify needs a file to be kept open on the device, causing problems during unmount. As for 1) -- since inotify is a char device the events are delivered when the user calls read (). This easily integrates in to an applications select() loop. I have a solution for 2) but I haven't implemented it yet, as I don't have the expertise. What I want to do is distinguish between some one holding a 'real' reference on an inode, and a reference that is used only for watching. This way in the unmount code we can make sure that no one is holding a real reference to an inode on the device, then while invalidating the inodes, clear the inodes watch list and send UNMOUNT events to the inotify device. Changes would have to be made so that inodes are kept in the inode cache when a watching reference is held. I would like some pointers on how to implement 2). I am not sure the code path that takes place on unmount, or the best place to change the inode cache semantics. I would also appreciate comments on the design in general and code review (this is my first kernel project). Attached is a patch implementing everything described in the email. John