From: Evgeniy Polyakov <zbr@ioremap.net>
To: Niraj kumar <niraj17@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [Question] inotify : process based filtering of events
Date: Sat, 20 Dec 2008 20:13:40 +0300 [thread overview]
Message-ID: <20081220171340.GA4655@ioremap.net> (raw)
In-Reply-To: <b82a89170812200513q1a27b62ap590fb6fbad930a@mail.gmail.com>
On Sat, Dec 20, 2008 at 06:43:01PM +0530, Niraj kumar (niraj17@gmail.com) wrote:
> I was hoping to add a flag (similar to IN_ATTRS that you have added)
> which, when used, will only collect events for the calling
> process and it's children...
With nested attributes patch you can add your own callback which will
check private list of interested pids and only add event into the queue
when current credentials match stored data. IMHO that will br much
smaller amount of work than extending inotify with new flag and redoing
new event structure processing. But it is up to you to decide of course
:)
--
Evgeniy Polyakov
prev parent reply other threads:[~2008-12-20 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 6:51 [Question] inotify : process based filtering of events Niraj kumar
2008-12-20 10:40 ` Evgeniy Polyakov
2008-12-20 13:13 ` Niraj kumar
2008-12-20 17:13 ` Evgeniy Polyakov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081220171340.GA4655@ioremap.net \
--to=zbr@ioremap.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niraj17@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox