From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [8/8] Fix fsnotify short comings (single fd with recursive notifications). Date: Mon, 8 Apr 2013 16:22:55 +0100 Message-ID: <20130408152255.GR4068@ZenIV.linux.org.uk> References: <516299A5.8030109@panasas.com> <51629FDB.5090708@panasas.com> <5162CD55.6040205@cea.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Boaz Harrosh , Steven Whitehouse , Steve Dickson , Jeff Layton , lsf-pc@lists.linux-foundation.org, linux-fsdevel , Ganesha NFS List , Frank S Filz , "J. Bruce Fields" , "Lieb, Jim" , Venkateswararao Jujjuri To: DENIEL Philippe Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:60285 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935977Ab3DHPXH (ORCPT ); Mon, 8 Apr 2013 11:23:07 -0400 Content-Disposition: inline In-Reply-To: <5162CD55.6040205@cea.fr> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Mon, Apr 08, 2013 at 03:59:49PM +0200, DENIEL Philippe wrote: > What I have seen was this: > - if dnotify() is used, it gets every events. If used on a > directory, it will get every creation and deletion. But it is not > recursive, so we need to use dnotify on every inode we manage. > - if fanotify is used, it is recursive and by using it on the > root of a filesystem, then you have events from the whole underlying > tree. The trouble is that deletion seem not to be caught. All *notify APIs are broken by design, film at 11... See also: "Doctor, it hurts when I do it"