From: Eric Paris <eparis@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Andreas Dilger <adilger@sun.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
malware-list@dmesg.printk.net, Valdis.Kletnieks@vt.edu,
greg@kroah.com, jcm@redhat.com, douglas.leeder@sophos.com,
tytso@mit.edu, arjan@infradead.org, david@lang.hm,
jengelh@medozas.de, aviro@redhat.com, mrkafk@gmail.com,
alexl@redhat.com, jack@suse.cz, tvrtko.ursulin@sophos.com,
a.p.zijlstra@chello.nl, hch@infradead.org,
alan@lxorguk.ukuu.org.uk, mmorley@hcl.in, pavel@suse.cz
Subject: Re: fanotify - overall design before I start sending patches
Date: Wed, 29 Jul 2009 16:14:15 -0400 [thread overview]
Message-ID: <1248898455.2597.59.camel@localhost> (raw)
In-Reply-To: <20090727192342.GA27895@shareable.org>
On Mon, 2009-07-27 at 20:23 +0100, Jamie Lokier wrote:
> Andreas Dilger wrote:
> > On Jul 25, 2009 01:29 +0100, Jamie Lokier wrote:
> > > Eric Paris wrote:
> What's wrong with fanotify-using applications generating events when
> they modify files themselves?
>
> An example was given where app A gets an event and modifies the file,
> then app B gets an event and modifies the file, and app A... cycling.
No the example was the 'open' which the kernel does on behalf of the
listener. I'm thinking now I should only exclude
OPEN
OPEN_PERM
ACCESS_PERM
as those are the only 3 event types I can see deadlock/recursion
problems with.
next prev parent reply other threads:[~2009-07-29 20:16 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 20:13 fanotify - overall design before I start sending patches Eric Paris
2009-07-24 20:48 ` david
2009-07-24 21:01 ` Eric Paris
2009-07-24 21:44 ` Jamie Lokier
2009-07-27 17:52 ` Evgeniy Polyakov
2009-07-29 20:11 ` Eric Paris
2009-07-24 21:00 ` Andreas Dilger
2009-07-24 21:21 ` Eric Paris
2009-07-24 22:42 ` Andreas Dilger
2009-07-24 23:01 ` Jamie Lokier
2009-07-24 22:48 ` Jamie Lokier
2009-07-24 23:25 ` Eric Paris
2009-07-24 23:46 ` Jamie Lokier
2009-07-24 23:49 ` Eric Paris
2009-07-25 0:29 ` Jamie Lokier
2009-07-27 18:33 ` Andreas Dilger
2009-07-27 19:23 ` Jamie Lokier
2009-07-28 17:59 ` Andreas Dilger
2009-07-29 20:14 ` Eric Paris [this message]
2009-07-29 20:12 ` Eric Paris
2009-07-29 20:07 ` Eric Paris
2009-07-27 16:54 ` Jan Kara
2009-07-25 14:22 ` Niraj kumar
2009-07-29 20:08 ` Eric Paris
2009-07-28 11:48 ` Jon Masters
2009-07-29 20:20 ` Eric Paris
2009-08-03 16:23 ` Christoph Hellwig
2009-08-03 16:55 ` Eric Paris
2009-08-03 18:04 ` Christoph Hellwig
2009-08-03 18:13 ` Eric Paris
2009-08-04 16:09 ` Tvrtko Ursulin
2009-08-04 16:27 ` Eric Paris
2009-08-04 16:39 ` Tvrtko Ursulin
2009-08-04 17:22 ` Valdis.Kletnieks
2009-08-04 18:20 ` John Stoffel
2009-08-04 18:50 ` Eric Paris
2009-08-05 9:32 ` Tvrtko Ursulin
2009-08-04 16:34 ` Tvrtko Ursulin
2009-08-05 10:12 ` Douglas Leeder
2009-08-05 10:35 ` Douglas Leeder
2009-08-05 2:05 ` Pavel Machek
2009-08-05 16:46 ` Tvrtko Ursulin
2009-08-06 10:10 ` Pavel Machek
2009-08-06 10:20 ` Tvrtko Ursulin
2009-08-06 10:24 ` Pavel Machek
2009-08-06 10:20 ` Douglas Leeder
2009-08-06 10:22 ` Pavel Machek
2009-08-07 8:59 ` Jamie Lokier
2009-08-06 10:29 ` Peter Zijlstra
2009-08-06 10:59 ` Tvrtko Ursulin
2009-08-06 11:23 ` Peter Zijlstra
2009-08-06 12:48 ` Tvrtko Ursulin
2009-08-06 12:58 ` Alan Cox
2009-08-06 18:18 ` Eric Paris
2009-08-06 13:50 ` Kernel Event Notification Subsystem (was: fanotify - overall design before I start sending patches) Al Boldi
2009-08-06 18:18 ` fanotify - overall design before I start sending patches Eric Paris
2009-08-07 16:36 ` Miklos Szeredi
2009-08-07 17:43 ` Eric Paris
2009-08-08 10:36 ` Pavel Machek
2009-08-10 10:03 ` Miklos Szeredi
2009-08-08 10:34 ` Pavel Machek
2009-08-06 11:24 ` Pavel Machek
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=1248898455.2597.59.camel@localhost \
--to=eparis@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=adilger@sun.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alexl@redhat.com \
--cc=arjan@infradead.org \
--cc=aviro@redhat.com \
--cc=david@lang.hm \
--cc=douglas.leeder@sophos.com \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jamie@shareable.org \
--cc=jcm@redhat.com \
--cc=jengelh@medozas.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malware-list@dmesg.printk.net \
--cc=mmorley@hcl.in \
--cc=mrkafk@gmail.com \
--cc=pavel@suse.cz \
--cc=tvrtko.ursulin@sophos.com \
--cc=tytso@mit.edu \
/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