From: Beata Michalska <b.michalska@samsung.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org
Cc: jack@suse.cz, tytso@mit.edu, adilger.kernel@dilger.ca,
hughd@google.com, lczerner@redhat.com, hch@infradead.org,
linux-ext4@vger.kernel.org, linux-mm@kvack.org,
kyungmin.park@samsung.com, kmpark@infradead.org
Subject: [RFC v2 0/4] fs: Add generic file system event notifications
Date: Mon, 27 Apr 2015 13:51:40 +0200 [thread overview]
Message-ID: <1430135504-24334-1-git-send-email-b.michalska@samsung.com> (raw)
Hi All,
This series is a follow-up of the RFC patchset for generic filesystem
events interface [1]. As there have been some rather significant changes
to the synchronization method being used, more extensive testing (stress
testing) has been performed (thus the delay).
Changes from v1:
- Improved synchronization: switched to RCU accompanied with
ref counting mechanism
- Limiting scope of supported event types along with default
event codes
- Slightly modified configuration (event types followed by arguments
where required)
- Updated documentation
- Unified naming for netlink attributes
- Updated netlink message format to include dev minor:major numbers
despite the filesystem type
- Switched to single cmd id for messages
- Removed the per-config-entry ids
---
[1] https://lkml.org/lkml/2015/4/15/46
---
Beata Michalska (4):
fs: Add generic file system event notifications
ext4: Add helper function to mark group as corrupted
ext4: Add support for generic FS events
shmem: Add support for generic FS events
Documentation/filesystems/events.txt | 231 ++++++++++
fs/Makefile | 1 +
fs/events/Makefile | 6 +
fs/events/fs_event.c | 770 ++++++++++++++++++++++++++++++++++
fs/events/fs_event.h | 25 ++
fs/events/fs_event_netlink.c | 99 +++++
fs/ext4/balloc.c | 25 +-
fs/ext4/ext4.h | 10 +
fs/ext4/ialloc.c | 5 +-
fs/ext4/inode.c | 2 +-
fs/ext4/mballoc.c | 17 +-
fs/ext4/resize.c | 1 +
fs/ext4/super.c | 39 ++
fs/namespace.c | 1 +
include/linux/fs.h | 6 +-
include/linux/fs_event.h | 58 +++
include/uapi/linux/fs_event.h | 54 +++
include/uapi/linux/genetlink.h | 1 +
mm/shmem.c | 33 +-
net/netlink/genetlink.c | 7 +-
20 files changed, 1357 insertions(+), 34 deletions(-)
create mode 100644 Documentation/filesystems/events.txt
create mode 100644 fs/events/Makefile
create mode 100644 fs/events/fs_event.c
create mode 100644 fs/events/fs_event.h
create mode 100644 fs/events/fs_event_netlink.c
create mode 100644 include/linux/fs_event.h
create mode 100644 include/uapi/linux/fs_event.h
--
1.7.9.5
next reply other threads:[~2015-04-27 11:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 11:51 Beata Michalska [this message]
2015-04-27 11:51 ` [RFC v2 1/4] fs: Add generic file system event notifications Beata Michalska
2015-04-27 14:24 ` Greg KH
2015-04-27 15:08 ` Beata Michalska
2015-04-27 15:37 ` Greg KH
2015-04-28 9:05 ` Beata Michalska
2015-04-28 13:56 ` Jan Kara
2015-04-28 14:09 ` Greg KH
2015-04-28 14:46 ` Beata Michalska
2015-04-28 17:39 ` Greg KH
2015-04-29 7:03 ` Beata Michalska
2015-04-29 7:42 ` Jan Kara
2015-04-29 9:13 ` Greg KH
2015-04-29 11:10 ` Beata Michalska
2015-04-29 13:45 ` Greg KH
2015-04-29 15:48 ` Beata Michalska
2015-04-29 15:55 ` Greg KH
2015-04-30 8:21 ` Beata Michalska
2015-05-05 12:16 ` Beata Michalska
2015-05-07 11:57 ` Beata Michalska
2015-05-26 16:39 ` Beata Michalska
2015-05-27 2:34 ` Greg KH
2015-05-27 13:32 ` Beata Michalska
2015-04-27 11:51 ` [RFC v2 2/4] ext4: Add helper function to mark group as corrupted Beata Michalska
2015-04-27 11:51 ` [RFC v2 3/4] ext4: Add support for generic FS events Beata Michalska
2015-04-27 11:51 ` [RFC v2 4/4] shmem: " Beata Michalska
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=1430135504-24334-1-git-send-email-b.michalska@samsung.com \
--to=b.michalska@samsung.com \
--cc=adilger.kernel@dilger.ca \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=kmpark@infradead.org \
--cc=kyungmin.park@samsung.com \
--cc=lczerner@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tytso@mit.edu \
/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).