[lkml]   [2009]   [Aug]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: fanotify - overall design before I start sending patches
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)


 \ /
  Last update: 2009-08-03 18:59    [W:0.190 / U:5.340 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site