Re: fanotify - overall design before I start sending patches

[Eric Paris]

On Mon, 2009-08-03 at 12:23 -0400, Christoph Hellwig wrote:
> Before we get started:  You promised yo get rid of the dnotify and
> inotify fields in the inode when moving over those two to fsnotify.
> While the dnotify fields are gone the inotify_watches and inotify_mutex
> fields are still around.  I'd really like to see this done before we
> move on.

In linux-next you will find that those fields are completely unused and
the kernel can be compiled without them with 0 lose of functionality
(they are still used in linus's kernel by the audit system)

The only reason I didn't remove them entirely is because the inotify
kernel interface is EXPORT_SYMBOL.  I plan to leave it around for a
little bit until I'm sure out of tree users don't exist or at least had
enough time to realize they need to use fsnotify.

For all situations I know of at least, those 2 fields can be safely
compiled out.  (aka !CONFIG_INOTIFY)

-Eric

--
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/