Brian Rogers b962e7312a inotify: do not send a block of zeros when no pathname is available ...

When an event has no pathname, there's no need to pad it with a null byte and
therefore generate an inotify_event sized block of zeros. This fixes a
regression introduced by commit 0db501bd0610ee0c0aca84d927f90bcccd09e2bd where
my system wouldn't finish booting because some process was being confused by
this.

Signed-off-by: Brian Rogers <brian@xyzw.org>
Signed-off-by: Eric Paris <eparis@redhat.com>

2009-08-28 10:03:06 -04:00

..

dnotify

fsnotify: use def_bool in kconfig instead of letting the user choose

2009-07-21 15:26:26 -04:00

inotify

inotify: do not send a block of zeros when no pathname is available

2009-08-28 10:03:06 -04:00

fsnotify.c

inotify: use GFP_NOFS under potential memory pressure

2009-07-21 15:26:27 -04:00

fsnotify.h

fsnotify: generic notification queue and waitq

2009-06-11 14:57:53 -04:00

group.c

fsnotify: generic notification queue and waitq

2009-06-11 14:57:53 -04:00

inode_mark.c

fsnotify: allow groups to set freeing_mark to null

2009-06-11 14:57:55 -04:00

Kconfig

fsnotify: use def_bool in kconfig instead of letting the user choose

2009-07-21 15:26:26 -04:00

Makefile

fsnotify: add marks to inodes so groups can interpret how to handle those inodes

2009-06-11 14:57:53 -04:00

notification.c

inotify: tail drop inotify q_overflow events

2009-08-17 13:37:37 -07:00