From: Chris Wright <chrisw@osdl.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Chris Wright <chrisw@osdl.org>, Robert Love <rml@novell.com>,
ttb@tentacle.dhs.org, linux-audit@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH 1/2] fsnotify
Date: Mon, 11 Jul 2005 10:25:36 -0700 [thread overview]
Message-ID: <20050711172536.GI19052@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1121086366.27264.108.camel@hades.cambridge.redhat.com>
* David Woodhouse (dwmw2@infradead.org) wrote:
> What would make sense, perhaps, would be to actually merge those hooks;
> not just a cosmetic amalgamation of the calling sites. Currently, each
> of inotify and the audit code does its own filtering when its hooks are
> triggered, and then acts upon the event only if it affects a watched
> inode.
That's exactly what my intention was by posting this. The hook site is
just enough to get the conversation going. The really useful bits to
merge are at inode watch level.
thanks,
-chris
prev parent reply other threads:[~2005-07-11 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 1:24 [RFC/PATCH 0/2] fsnotify/inotify split Chris Wright
2005-07-09 1:26 ` [RFC/PATCH 1/2] fsnotify Chris Wright
2005-07-09 1:28 ` [RFC/PATCH 2/2] inotify Chris Wright
2005-07-11 12:52 ` [RFC/PATCH 1/2] fsnotify David Woodhouse
2005-07-11 15:57 ` Robert Love
2005-07-11 17:25 ` Chris Wright [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=20050711172536.GI19052@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=dwmw2@infradead.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=ttb@tentacle.dhs.org \
/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;
as well as URLs for NNTP newsgroup(s).