public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott James Remnant <scott@ubuntu.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: inotify regression, missing events
Date: Mon, 13 Jul 2009 13:21:09 +0100	[thread overview]
Message-ID: <1247487669.14981.18.camel@quest> (raw)
In-Reply-To: <1247313019.2791.1.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 815 bytes --]

On Sat, 2009-07-11 at 07:50 -0400, Eric Paris wrote:

> On Sat, 2009-07-11 at 17:02 +0100, Scott James Remnant wrote:
> > 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.
> 
In other words, when the second deleted-file-in-a-directory event comes
through, it gets ignored because there's already a
"deleted-file-in-a-directory" event for that directory?

Scott
-- 
Scott James Remnant
scott@ubuntu.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-07-13 12:20 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
2009-07-13 12:21   ` Scott James Remnant [this message]
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=1247487669.14981.18.camel@quest \
    --to=scott@ubuntu.com \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox