The patch titled Subject: fanotify: fix missing break has been added to the -mm tree. Its filename is fanotify-fix-missing-break.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Eric Paris <eparis@xxxxxxxxxx> Subject: fanotify: fix missing break Anders Blomdell noted in 2010 that Fanotify lost events and provided a test case. Eric Paris confirmed it was a bug and posted a fix to the list https://groups.google.com/forum/?fromgroups=#!topic/linux.kernel/RrJfTfyW2BE but never applied it. Repeated attempts over time to actually get him to apply it have never had a reply from anyone who has raised it So apply it anyway Signed-off-by: Alan Cox <alan@xxxxxxxxxxxxxxx> Reported-by: Anders Blomdell <anders.blomdell@xxxxxxxxxxxxxx> Cc: Eric Paris <eparis@xxxxxxxxxx> Cc: <stable@xxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/notify/fanotify/fanotify.c | 1 + 1 file changed, 1 insertion(+) diff -puN fs/notify/fanotify/fanotify.c~fanotify-fix-missing-break fs/notify/fanotify/fanotify.c --- a/fs/notify/fanotify/fanotify.c~fanotify-fix-missing-break +++ a/fs/notify/fanotify/fanotify.c @@ -21,6 +21,7 @@ static bool should_merge(struct fsnotify if ((old->path.mnt == new->path.mnt) && (old->path.dentry == new->path.dentry)) return true; + break; case (FSNOTIFY_EVENT_NONE): return true; default: _ Patches currently in -mm which might be from eparis@xxxxxxxxxx are fanotify-fix-missing-break.patch linux-next.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html