Correctly handle IN_Q_OVERFLOW events.

This commit should fix a regression introduced with commit
d334049eed6b1136a9d224a3ca17aa66fea5215a.

Issue reported by Tomi Belan @TomiBelan.

1 files changed, 4 insertions, 4 deletions

diff --git a/python2/pyinotify.py b/python2/pyinotify.py
index 27f0f4e..ec99b71 100755
--- a/python2/pyinotify.py
+++ b/python2/pyinotify.py
@@ -1281,10 +1281,10 @@ class Notifier:
         while self._eventq:
             raw_event = self._eventq.popleft()  # pop next event
             watch_ = self._watch_manager.get_watch(raw_event.wd)
-            if watch_ is None:
-                # Not really sure how we ended up here, nor how we should
-                # handle these types of events and if it is appropriate to
-                # completly skip them (like we are doing here).
+            # Not really sure how we ended up here, nor how we should
+            # handle these types of events and if it is appropriate to
+            # completly skip them (like we are doing here).
+            if (watch_ is None) and not (raw_event.mask & IN_Q_OVERFLOW):
                 if not (raw_event.mask & IN_IGNORED):
                     log.warning("Unable to retrieve Watch object associated to %s",
                                 repr(raw_event))