From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Paris Subject: Re: fanotify - overall design before I start sending patches Date: Wed, 29 Jul 2009 16:14:15 -0400 Message-ID: <1248898455.2597.59.camel@localhost> References: <1248466429.3567.82.camel@localhost> <20090724224813.GK27755@shareable.org> <1248479367.3567.133.camel@localhost> <20090725002916.GB13556@shareable.org> <20090727183354.GM4231@webber.adilger.int> <20090727192342.GA27895@shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Andreas Dilger , jack-AlSwsSmVLrQ@public.gmane.org, jengelh-nopoi9nDyk+ELgA04lAiVw@public.gmane.org, pavel-AlSwsSmVLrQ@public.gmane.org, alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org, malware-list-h+Im9A44IAFcMpApZELgcQ@public.gmane.org, mrkafk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org, a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org, jcm-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, alexl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, arjan-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org, david-gFPdbfVZQbY@public.gmane.org, Valdis.Kletnieks-PjAqaU27lzQ@public.gmane.org, douglas.leeder-j34lQMj1tz/QT0dZR+AlfA@public.gmane.org, aviro-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jamie Lokier Return-path: In-Reply-To: <20090727192342.GA27895-yetKDKU6eevNLxjTenLetw@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: malware-list-bounces-h+Im9A44IAFcMpApZELgcQ@public.gmane.org Errors-To: malware-list-bounces-h+Im9A44IAFcMpApZELgcQ@public.gmane.org List-Id: linux-fsdevel.vger.kernel.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.