All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Scott James Remnant <scott@ubuntu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: inotify regression, missing events
Date: Sat, 11 Jul 2009 07:50:19 -0400	[thread overview]
Message-ID: <1247313019.2791.1.camel@localhost> (raw)
In-Reply-To: <1247328127.4003.6.camel@wing-commander>

On Sat, 2009-07-11 at 17:02 +0100, Scott James Remnant wrote:
> Hey folks,
> 
> Looks like there's a regression with inotify since the rewrite to use
> fanotify.  Events are simply missing and not being delivered to
> userspace.
> 
> Here's a simple test case, just compile and run it:

I bet I know exactly what it is (notification.c tail merge code isn't
comparing filename only inode+mask) but I'm walking out of the house.
I'll try my theory later tonight and post a patch.

Stupid Eric, Stupid.

-Eric


  reply	other threads:[~2009-07-11 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11 16:02 inotify regression, missing events Scott James Remnant
2009-07-11 11:50 ` Eric Paris [this message]
2009-07-13 12:21   ` Scott James Remnant
2009-07-13 13:43     ` Eric Paris
2009-07-25 22:23       ` Rafael J. Wysocki
2009-07-25 22:27         ` Eric Paris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1247313019.2791.1.camel@localhost \
    --to=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott@ubuntu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.