Re: PROBLEM: 2.6.35.7 to 3.0 Inotify events missing

From: Al Viro
Date: Fri Aug 19 2011 - 21:29:56 EST


On Sat, Aug 20, 2011 at 12:37:56AM +0100, Jamie Lokier wrote:

> Possible solution:

> Then this can be solved, in principle (if there's no better way), by
> watching a "virtual directory" that gets all events for when the
> access doesn't have a parent directory. There needs to be some way to
> watch it, and some way to get the appropriate file from the event (as
> there is no real directory. Or maybe there could be a virtual
> filesystem (like /proc, /sys etc.) containing a magic directory that
> receives these inode-only events, such that lookups in that directory
> yield the affected file. Exactly as if the directory contains a hard
> link to every file, perhaps a text encoding of the handles passed
> through sys_open_by_handle_at.

There is a better way - stop using idiotify... It has always been a
mistake, driven down our throats by filemangler and desktop crowd.
Broken in many, _many_ respects... Deprecate that crap, remove it
completely in a couple of revisions, let these clowns cope. Yeah,
yeah, I know... Not going to happen ;-/ One can dream, though...
--
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/