From: Amy Griffis <amy.griffis@hp.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org,
John McCutchan <john@johnmccutchan.com>,
Robert Love <rlove@rlove.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] inotify: split kernel API from userspace support
Date: Wed, 7 Jun 2006 23:59:10 -0400 [thread overview]
Message-ID: <20060608035910.GA1969@zk3.dec.com> (raw)
In-Reply-To: <20060606210619.GE4044@ucw.cz>
Pavel Machek wrote: [Tue Jun 06 2006, 05:06:19PM EDT]
> > Here is a more descriptive changelog message for this patch:
> >
> > This patch introduces a kernel API for inotify, making it possible for
> > kernel modules to benefit from inotify's mechanism for watching
> > inodes.
>
> What are proposed uses of this API?
Currently there are two uses of this API.
The first user is the code that provides inotify support to userspace,
which lives in inotify_user.c in this patch.
The second user is an audit patch which provides path-based rules via
inotify directory events. An inotify kernel API allows audit to take
advantage of inotify's hooks, list management, and inode removal
handling, instead of duplicating that functionality.
I'll send the audit patch in a new thread.
Amy
prev parent reply other threads:[~2006-06-08 3:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 15:07 [PATCH] inotify: split kernel API from userspace support Amy Griffis
2006-06-01 15:08 ` [PATCH 2/5] inotify: add name's inode to event handler Amy Griffis
2006-06-01 15:10 ` [PATCH 3/5] inotify: add interfaces to kernel API Amy Griffis
2006-06-01 15:10 ` [PATCH 4/5] inotify: allow watch removal from event handler Amy Griffis
2006-06-01 15:11 ` [PATCH 5/5] inotify: update kernel documentation Amy Griffis
2006-06-01 17:46 ` [PATCH] inotify: split kernel API from userspace support Robert Love
[not found] ` <1149216713.2865.0.camel@localhost.localdomain>
2006-06-02 2:51 ` John McCutchan
2006-06-02 12:32 ` Amy Griffis
2006-06-06 21:06 ` Pavel Machek
2006-06-08 3:59 ` Amy Griffis [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=20060608035910.GA1969@zk3.dec.com \
--to=amy.griffis@hp.com \
--cc=akpm@osdl.org \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rlove@rlove.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