kernel-fxtec-pro1x/fs/notify/fanotify/Kconfig

config FANOTIFY
	bool "Filesystem wide access notification"
	select FSNOTIFY
	select ANON_INODES
	default n
	---help---
	   Say Y here to enable fanotify suport.  fanotify is a file access
	   notification system which differs from inotify in that it sends
	   an open file descriptor to the userspace listener along with
	   the event.

	   If unsure, say Y.

config FANOTIFY_ACCESS_PERMISSIONS
	bool "fanotify permissions checking"
	depends on FANOTIFY
	depends on SECURITY
	default n
	---help---
	   Say Y here is you want fanotify listeners to be able to make permissions
	   decisions concerning filesystem events.  This is used by some fanotify
	   listeners which need to scan files before allowing the system access to
	   use those files.  This is used by some anti-malware vendors and by some
	   hierarchical storage managent systems.

	   If unsure, say N.
fanotify: fscking all notification system 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. This patch just implements the basics of the fsnotify functions. Signed-off-by: Eric Paris <eparis@redhat.com> 2009-12-17 19:24:25 -07:00			`config FANOTIFY`
			`bool "Filesystem wide access notification"`
			`select FSNOTIFY`
fanotify: select ANON_INODES. fanotify references anon_inode_getfd(), which is only available with ANON_INODES enabled. Presently this bails out with the following: LD vmlinux fs/built-in.o: In function `sys_fanotify_init': (.text+0x26d1c): undefined reference to `anon_inode_getfd' make: *** [vmlinux] Error 1 which is trivially corrected by adding an ANON_INODES select. Signed-off-by: Paul Mundt <lethal@linux-sh.org> Signed-off-by: Eric Paris <eparis@redhat.com> 2009-12-17 19:24:26 -07:00			`select ANON_INODES`
fanotify: default Kconfig to n fanotify has default to y in linux-next since it's inception but default to n in the final push to Linus. Signed-off-by: Eric Paris <eparis@redhat.com> 2010-05-27 07:29:37 -06:00			`default n`
fanotify: fscking all notification system 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. This patch just implements the basics of the fsnotify functions. Signed-off-by: Eric Paris <eparis@redhat.com> 2009-12-17 19:24:25 -07:00			`---help---`
			`Say Y here to enable fanotify suport. fanotify is a file access`
			`notification system which differs from inotify in that it sends`
Kconfig: typo: and -> an Signed-off-by: Michael Witten <mfwitten@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz> 2010-11-01 11:50:12 -06:00			`an open file descriptor to the userspace listener along with`
fanotify: fscking all notification system 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. This patch just implements the basics of the fsnotify functions. Signed-off-by: Eric Paris <eparis@redhat.com> 2009-12-17 19:24:25 -07:00			`the event.`

			`If unsure, say Y.`
fanotify: permissions and blocking This is the backend work needed for fanotify to support the new FS_OPEN_PERM and FS_ACCESS_PERM fsnotify events. This is done using the new fsnotify secondary queue. No userspace interface is provided actually respond to or request these events. Signed-off-by: Eric Paris <eparis@redhat.com> 2009-12-17 19:24:34 -07:00
			`config FANOTIFY_ACCESS_PERMISSIONS`
			`bool "fanotify permissions checking"`
			`depends on FANOTIFY`
			`depends on SECURITY`
			`default n`
			`---help---`
			`Say Y here is you want fanotify listeners to be able to make permissions`
			`decisions concerning filesystem events. This is used by some fanotify`
			`listeners which need to scan files before allowing the system access to`
			`use those files. This is used by some anti-malware vendors and by some`
			`hierarchical storage managent systems.`

			`If unsure, say N.`