summaryrefslogtreecommitdiff
path: root/include/linux/fanotify.h
diff options
context:
space:
mode:
authorEric Paris <eparis@redhat.com>2010-10-29 01:21:57 +0400
committerEric Paris <eparis@redhat.com>2010-10-29 01:22:14 +0400
commit2529a0df0f64dab1f60ae08e038b89c53a6b4c02 (patch)
tree59f73938d84b78b535c91282677054d1f3dd1697 /include/linux/fanotify.h
parent5322a59f14e4cae5f878b9c0c5612d403c230d7f (diff)
downloadlinux-2529a0df0f64dab1f60ae08e038b89c53a6b4c02.tar.xz
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>
Diffstat (limited to 'include/linux/fanotify.h')
-rw-r--r--include/linux/fanotify.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/linux/fanotify.h b/include/linux/fanotify.h
index a97c96d28c07..ed479b6fef7b 100644
--- a/include/linux/fanotify.h
+++ b/include/linux/fanotify.h
@@ -12,7 +12,6 @@
#define FAN_EVENT_ON_CHILD 0x08000000 /* interested in child events */
-/* FIXME currently Q's have no limit.... */
#define FAN_Q_OVERFLOW 0x00004000 /* Event queued overflowed */
#define FAN_OPEN_PERM 0x00010000 /* File open in perm check */