[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090817015149.15099.12171.stgit@paris.rdu.redhat.com>
Date: Sun, 16 Aug 2009 21:51:49 -0400
From: Eric Paris <eparis@...hat.com>
To: linux-kernel@...r.kernel.org, fs-devel@...r.kernel.org
Cc: torvalds@...ux-foundation.org, viro@...IV.linux.org.uk
Subject: [PATCH 2/3] inotify: tail drop inotify q_overflow events
In f44aebcc the tail drop logic of events with no file backing
(q_overflow and in_ignored) was reversed so IN_IGNORED events would never
be tail dropped. This now means that Q_OVERFLOW events are NOT tail
dropped. The fix is to not tail drop IN_IGNORED, but to tail drop
Q_OVERFLOW.
Signed-off-by: Eric Paris <eparis@...hat.com>
---
fs/notify/notification.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/fs/notify/notification.c b/fs/notify/notification.c
index 74b3cf3..3816d57 100644
--- a/fs/notify/notification.c
+++ b/fs/notify/notification.c
@@ -153,6 +153,10 @@ static bool event_compare(struct fsnotify_event *old, struct fsnotify_event *new
return true;
break;
case (FSNOTIFY_EVENT_NONE):
+ if (old->mask & FS_Q_OVERFLOW)
+ return true;
+ else if (old->mask & FS_IN_IGNORED)
+ return false;
return false;
};
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists