From mboxrd@z Thu Jan 1 00:00:00 1970 From: Niraj kumar Subject: Re: fanotify - overall design before I start sending patches Date: Sat, 25 Jul 2009 19:52:48 +0530 Message-ID: References: <1248466429.3567.82.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Eric Paris Return-path: Received: from an-out-0708.google.com ([209.85.132.241]:12365 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751076AbZGYOWt convert rfc822-to-8bit (ORCPT ); Sat, 25 Jul 2009 10:22:49 -0400 In-Reply-To: <1248466429.3567.82.camel@localhost> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > > - subtree notification. > =A0 =A0 =A0 =A0Currently to only watch /home and all of it's descenda= nts one must > either register a directed watch on every directory or use a global > listener. =A0The global listener with ignored_mask is not as bad as i= t > sounds in my testing, but decent subtree registration and notificatio= n > would be a big win in a lot of people's mind. Unless it's already covered in some way, I would also be interested in notification based on "process subtree". What this means is that for whatever notification a particular process requests, it's only interested in events generated by itself and it's children. This is useful in doing auditing for file system related access. -Niraj -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html