From: Robert Love <rml@novell.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Chris Wright <chrisw@osdl.org>,
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 11:57:09 -0400 [thread overview]
Message-ID: <1121097429.6596.49.camel@betsy> (raw)
In-Reply-To: <1121086366.27264.108.camel@hades.cambridge.redhat.com>
On Mon, 2005-07-11 at 13:52 +0100, David Woodhouse wrote:
> To be honest, I don't really see that this is in any way better than
> what we had before. Yes, two different pieces of code actually use hooks
> in similar places in the VFS code. But this 'infrastructure' just to
> share those hooks is overkill as far as I can tell. It really isn't any
> better than having both inotify and audit hooks side by side where we
> can actually see what's going on at a glance. In fact, it's worse.
I think what makes this patch look superfluous is that Chris added a set
of wrappers for dnotify, too.
In the inotify patch, the fsnotify wrappers call directly into the
inotify and dnotify interfaces and they do consolidate code and clean
things up. I added fsnotify at hch's request.
Now that audit is coming along, fsnotify makes even more sense.
I would like to share some more code at a lower level, though, as you
pointed out.
I planned to look at redoing dnotify entirely on top of inotify, once
inotify is in the kernel proper, for example.
Robert Love
next prev parent reply other threads:[~2005-07-11 16:01 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 [this message]
2005-07-11 17:25 ` Chris Wright
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=1121097429.6596.49.camel@betsy \
--to=rml@novell.com \
--cc=chrisw@osdl.org \
--cc=dwmw2@infradead.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.