From mboxrd@z Thu Jan 1 00:00:00 1970 From: Evgeniy Polyakov Subject: Re: [PATCH 1/9] task_struct: add PF_NONOTIFY for fanotify to use Date: Sat, 29 Aug 2009 02:36:26 +0400 Message-ID: <20090828223626.GA8283@ioremap.net> References: <20090828185542.8014.22791.stgit@paris.rdu.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org, davem@davemloft.net, viro@zeniv.linux.org.uk, alan@linux.intel.com, hch@infradead.org To: Eric Paris Return-path: Content-Disposition: inline In-Reply-To: <20090828185542.8014.22791.stgit@paris.rdu.redhat.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hi. On Fri, Aug 28, 2009 at 02:55:42PM -0400, Eric Paris (eparis@redhat.com) wrote: > Since fanotify opens file descriptors inside the kernel for it's listeners > it needs a way to make sure that 2 fanotify listeners, both which listen to > open events do not continuously see each others open events (and get into a > livelock reporting on each other's activity). This fix is to create a new > tast_struct flags called PF_NONOTIFY. If this flag is set in a task no > fanotify events will be generated for that task. fanotify will set the > flag before and open call and will clear it immediately after. Is there a way to get old-school notifications with the object information instead of opened file desriptor, which may suffer rlimit problems and scalability issues with too many opened/closed descriptors? -- Evgeniy Polyakov