Eric Paris 08e53fcb0d inotify: start watch descriptor count at 1 ... The inotify_add_watch man page specifies that inotify_add_watch() will return a non-negative integer. However, historically the inotify watches started at 1, not at 0. Turns out that the inotifywait program provided by the inotify-tools package doesn't properly handle a 0 watch descriptor. In 7e790dd5 we changed from starting at 1 to starting at 0. This patch starts at 1, just like in previous kernels, but also just like in previous kernels it's possible for it to wrap back to 0. This preserves the kernel functionality exactly like it was before the patch (neither method broke the spec) Signed-off-by: Eric Paris <eparis@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2009-08-17 13:37:37 -07:00
..
inotify_fsnotify.c	notify: unused event private race	2009-08-17 13:37:37 -07:00
inotify_user.c	inotify: start watch descriptor count at 1	2009-08-17 13:37:37 -07:00
inotify.c	fsnotify: unified filesystem notification backend	2009-06-11 14:57:52 -04:00
inotify.h	inotify: inotify_destroy_mark_entry could get called twice	2009-06-19 12:42:48 -04:00
Kconfig	fsnotify: use def_bool in kconfig instead of letting the user choose	2009-07-21 15:26:26 -04:00
Makefile	inotify: reimplement inotify using fsnotify	2009-06-11 14:57:54 -04:00