From: John McCutchan <ttb@tentacle.dhs.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Robert Love <rml@novell.com>,
Nick Piggin <nickpiggin@yahoo.com.au>, Zach Brown <zab@zabbo.net>,
linux-kernel@vger.kernel.org,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] inotify, improved.
Date: Fri, 17 Jun 2005 13:57:36 -0400 [thread overview]
Message-ID: <20050617175735.GA2075@tentacle.dhs.org> (raw)
In-Reply-To: <42B2FD00.9060102@nortel.com>
On Fri, Jun 17, 2005 at 10:40:32AM -0600, Chris Friesen wrote:
> Robert Love wrote:
> >On Fri, 2005-06-17 at 09:37 -0600, Chris Friesen wrote:
>
> >>On a newsgroup someone was using inotify, but was asking if there was
> >>any way to also determine which process/user had caused the notification.
>
> >I have been hesitant, though. I do not want feature creep to be a
> >deterrent to acceptance into the Linux kernel.
>
> Absolutely.
>
> >I also think that there could be arguments about security.
> >...can we
> >say that read rights are enough for a unprivileged user to know that
> >root at pid 820 is writing the file? I don't know.
>
> I'm sure some reasonable rules could be determined. Maybe you'd need to
> be the owner of the file to get the extra info, with root able to
> monitor everything.
>
> Maybe there should be a way to load plugins into inotify (something like
> netfilter) so that people load modules to send themselves whatever
> information they want...
This is probably a good idea for the _audit_ system. Inotify was
designed to do 1 task well, and it should stay that way.
John
next prev parent reply other threads:[~2005-06-17 17:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 17:18 [patch] inotify Robert Love
2005-06-16 17:52 ` Zach Brown
2005-06-16 18:25 ` Robert Love
2005-06-17 1:30 ` Nick Piggin
2005-06-17 1:35 ` Robert Love
2005-06-17 15:15 ` [patch] inotify, improved Robert Love
2005-06-17 15:37 ` Chris Friesen
2005-06-17 15:44 ` Robert Love
2005-06-17 16:11 ` Valdis.Kletnieks
2005-06-17 16:29 ` Robert Love
2005-06-17 16:36 ` Chris Friesen
2005-06-17 16:43 ` Chris Wright
2005-06-17 16:46 ` Muli Ben-Yehuda
2005-06-17 16:40 ` Chris Friesen
2005-06-17 17:57 ` John McCutchan [this message]
2005-06-17 17:20 ` Zach Brown
2005-06-17 17:54 ` John McCutchan
2005-06-17 17:56 ` Zach Brown
2005-06-17 18:15 ` John McCutchan
2005-06-17 18:17 ` Zach Brown
2005-06-17 17:07 ` [patch] inotify Arnd Bergmann
2005-06-17 17:54 ` Christoph Hellwig
2005-06-17 18:12 ` John McCutchan
2005-06-17 18:16 ` Robert Love
2005-06-17 18:28 ` Christoph Hellwig
2005-06-17 18:38 ` Robert Love
2005-06-17 18:45 ` Christoph Hellwig
2005-06-17 18:54 ` Robert Love
2005-06-17 17:56 ` John McCutchan
2005-06-17 21:33 ` Andrew Morton
2005-06-17 21:40 ` Robert Love
2005-06-17 23:52 ` Robert Love
2005-06-21 0:51 ` Neil Brown
2005-06-21 2:15 ` John McCutchan
2005-06-21 2:29 ` Neil Brown
2005-06-21 2:43 ` John McCutchan
2005-06-21 15:55 ` Robert Love
2005-07-14 0:25 ` Neil Brown
2005-07-14 4:11 ` John McCutchan
2005-06-18 0:05 ` Arnd Bergmann
2005-06-18 0:57 ` Robert Love
2005-06-18 1:51 ` Chris Wedgwood
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=20050617175735.GA2075@tentacle.dhs.org \
--to=ttb@tentacle.dhs.org \
--cc=akpm@osdl.org \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rml@novell.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=zab@zabbo.net \
/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
Powered by JetHome