[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1273251421.15368.208.camel@localhost>
Date: Fri, 07 May 2010 12:57:01 -0400
From: Eric Paris <eparis@...hat.com>
To: Anders Blomdell <anders.blomdell@...trol.lth.se>
Cc: Eric Paris <eparis@...isplace.org>, linux-kernel@...r.kernel.org
Subject: Re: fanotify issues in 2.6.34-rc6-next-20100506
On Fri, 2010-05-07 at 11:24 +0200, Anders Blomdell wrote:
> seems to lose/corrupt events. For instance running 'fanotify -c /dir/to/watch'
> and then running the command 'cd /dir/to/watch ; touch a b c d e f g h i j k l'
> might generate (results are more or less random):
sometimes I'm not the sharpest knife in the drawer. switch statements
are hard.
diff --git a/fs/notify/fanotify/fanotify.c b/fs/notify/fanotify/fanotify.c
index bbcfccd..34c9661 100644
--- a/fs/notify/fanotify/fanotify.c
+++ b/fs/notify/fanotify/fanotify.c
@@ -21,6 +21,7 @@ static bool should_merge(struct fsnotify_event *old, struct fsnotify_event *new)
if ((old->path.mnt == new->path.mnt) &&
(old->path.dentry == new->path.dentry))
return true;
+ break;
case (FSNOTIFY_EVENT_NONE):
return true;
default:
--
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