Subject: Re: [PATCH 02/10] fanotify: fscking all notification system
From: Eric Paris <eparis@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linus-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk, hch@infradead.org,
       agruen@suse.de
In-Reply-To: <20091031184728.17244.73984.stgit@paris.rdu.redhat.com>
References: <20091031184721.17244.16465.stgit@paris.rdu.redhat.com>
	 <20091031184728.17244.73984.stgit@paris.rdu.redhat.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 06 Nov 2009 10:31:45 -0500
Message-Id: <1257521505.3289.10.camel@dhcp231-106.rdu.redhat.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 950
Lines: 20

On Sat, 2009-10-31 at 14:47 -0400, Eric Paris wrote:
> fanotify is a novel file notification system which bases notification on
> giving userspace both an event type (open, close, read, write) and an open
> file descriptor to the object in question.  This should address a number of
> races and problems with other notification systems like inotify and dnotify
> and should allow the future implementation of blocking or access controlled
> notification.  These are useful for on access scanners or hierachical storage
> management schemes.

I'm not hearing the negative feedback of the past and most everyone's
questions and concerns have been addressed.  Everyone ok if I drop these
into -next?

-Eric

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