From: Eric Paris <eparis@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: sfr@canb.auug.org.au, rlove@rlove.org,
malware-list@lists.printk.net, hch@infradead.org,
viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
john@johnmccutchan.com, alan@lxorguk.ukuu.org.uk
Subject: [PATCH -v1 00/11] fsnotify: unified filesystem notification backend
Date: Mon, 09 Feb 2009 16:28:52 -0500 [thread overview]
Message-ID: <1234214932.3724.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20090209211525.8985.13887.stgit@paris.rdu.redhat.com>
Whoops, forgot the cover note. So proceeding is an implementation of
fsnotify, a novel unified filesystem notification backend. This patch
set implements the backend and converts both dnotify and inotify to this
backend. This patch set reduced the size of struct inode if one uses
both dnotify and inotify.
I have patches which move the audit functionality which uses inotify to
fsnotify and I have patches which implement fanotify, my new on access
notification and access decisions to this backend, but just to keep the
series small I'm only sending fsnotify, dnotify and inotify changes.
I would love the most careful and scrutinizing eyes on patches 3, 9, 10
which implement the changes to inodes and introduce by far the most
complex locking, refcnt, and object lifetimes.
dnotify changes are in patch 5
inotify changes are in patch 11
Documentation/filesystems/fsnotify.txt | 192 ++++++++++
MAINTAINERS | 4
fs/inode.c | 10
fs/notify/Kconfig | 13
fs/notify/Makefile | 2
fs/notify/dnotify/Kconfig | 1
fs/notify/dnotify/dnotify.c | 449 +++++++++++++++++++-----
fs/notify/fsnotify.c | 91 +++++
fs/notify/fsnotify.h | 28 +
fs/notify/group.c | 207 +++++++++++
fs/notify/inode_mark.c | 330 ++++++++++++++++++
fs/notify/inotify/Kconfig | 20 -
fs/notify/inotify/Makefile | 2
fs/notify/inotify/inotify.h | 108 +++++
fs/notify/inotify/inotify_fsnotify.c | 176 +++++++++
fs/notify/inotify/inotify_kernel.c | 236 +++++++++++++
fs/notify/inotify/inotify_user.c | 598 ++++++++-------------------------
fs/notify/notification.c | 348 +++++++++++++++++++
include/linux/dcache.h | 3
include/linux/dnotify.h | 29 -
include/linux/fs.h | 6
include/linux/fsnotify.h | 255 ++++++++++----
include/linux/fsnotify_backend.h | 265 ++++++++++++++
23 files changed, 2735 insertions(+), 638 deletions(-)
prev parent reply other threads:[~2009-02-09 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 21:15 [PATCH -v1 01/11] fsnotify: unified filesystem notification backend Eric Paris
2009-02-09 21:15 ` [PATCH -v1 02/11] fsnotify: add group priorities Eric Paris
2009-02-09 21:15 ` [PATCH -v1 03/11] fsnotify: add in inode fsnotify markings Eric Paris
2009-02-12 21:57 ` Andrew Morton
2009-02-17 17:26 ` Eric Paris
2009-02-09 21:15 ` [PATCH -v1 04/11] fsnotify: parent event notification Eric Paris
2009-02-09 21:15 ` [PATCH -v1 05/11] dnotify: reimplement dnotify using fsnotify Eric Paris
2009-02-09 21:15 ` [PATCH -v1 06/11] fsnotify: generic notification queue and waitq Eric Paris
2009-02-09 21:15 ` [PATCH -v1 07/11] fsnotify: include pathnames with entries when possible Eric Paris
2009-02-09 21:16 ` [PATCH -v1 08/11] fsnotify: add correlations between events Eric Paris
2009-02-09 21:16 ` [PATCH -v1 09/11] fsnotify: fsnotify marks on inodes pin them in core Eric Paris
2009-02-09 21:16 ` [PATCH -v1 10/11] fsnotify: handle filesystem unmounts with fsnotify marks Eric Paris
2009-02-09 21:16 ` [PATCH -v1 11/11] inotify: reimplement inotify using fsnotify Eric Paris
2009-02-09 21:28 ` Eric Paris [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=1234214932.3724.11.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malware-list@lists.printk.net \
--cc=rlove@rlove.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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