kernel-hacking-2024-linux-s.../fs/notify
Eric Paris 2529a0df0f fsnotify: implement a default maximum queue depth
Currently fanotify has no maximum queue depth.  Since fanotify is
CAP_SYS_ADMIN only this does not pose a normal user DoS issue, but it
certianly is possible that an fanotify listener which can't keep up could
OOM the box.  This patch implements a default 16k depth.  This is the same
default depth used by inotify, but given fanotify's better queue merging in
many situations this queue will contain many additional useful events by
comparison.

Signed-off-by: Eric Paris <eparis@redhat.com>
2010-10-28 17:22:14 -04:00
..
dnotify fanotify: use both marks when possible 2010-07-28 10:18:55 -04:00
fanotify fsnotify: implement a default maximum queue depth 2010-10-28 17:22:14 -04:00
inotify llseek: automatically add .llseek fop 2010-10-15 15:53:27 +02:00
fsnotify.c fsnotify: call fsnotify_parent in perm events 2010-10-28 17:22:13 -04:00
fsnotify.h
group.c
inode_mark.c fsnotify: implement ordering between notifiers 2010-10-28 17:22:13 -04:00
Kconfig fanotify: allow fanotify to be built 2010-10-28 17:22:13 -04:00
Makefile
mark.c
notification.c Revert "fsnotify: store struct file not struct path" 2010-08-12 14:23:04 -07:00
vfsmount_mark.c fsnotify: implement ordering between notifiers 2010-10-28 17:22:13 -04:00