DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=agEISiRW2NUfWHO2lCgZ7KpGGY0mn5N9da5WVldBica+CAv4Mvc4Fw0RDqjnew/YRJ
         Talb9wT9aXXOkvOj4YlVE97rh585QHqifs+Paynz/bg450cenkw4f2OC2fuWJP1MPN/1
         y6LDgqJfgvIc0YQd8gYwT3lbeNAX7BpA46g4A=
MIME-Version: 1.0
In-Reply-To: <1248466429.3567.82.camel@localhost>
References: <1248466429.3567.82.camel@localhost>
Date: Sat, 25 Jul 2009 19:52:48 +0530
Message-ID: <b82a89170907250722o572e741dq372ab11faf58261@mail.gmail.com>
Subject: Re: fanotify - overall design before I start sending patches
From: Niraj kumar <niraj17@gmail.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 950
Lines: 20

>
> - subtree notification.
> ? ? ? ?Currently to only watch /home and all of it's descendants one must
> either register a directed watch on every directory or use a global
> listener. ?The global listener with ignored_mask is not as bad as it
> sounds in my testing, but decent subtree registration and notification
> 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-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/