linux-kernel - Re: [PATCH 02/10] fanotify: fscking all notification system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 06 Nov 2009 10:31:45 -0500
From:	Eric Paris <eparis@...hat.com>
To:	linux-kernel@...r.kernel.org
Cc:	linus-fsdevel@...r.kernel.org, viro@...iv.linux.org.uk,
	hch@...radead.org, agruen@...e.de
Subject: Re: [PATCH 02/10] fanotify: fscking all notification system

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/