linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Beata Michalska <b.michalska@samsung.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-api@vger.kernel.org
Cc: greg@kroah.com, 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 v3 0/4] fs: Add generic file system event notifications
Date: Tue, 16 Jun 2015 15:09:29 +0200	[thread overview]
Message-ID: <1434460173-18427-1-git-send-email-b.michalska@samsung.com> (raw)

Hi All,

First of all, apologies for the delay: illness ruled out my plans
for having this out for a review as intended.

Anyway this is an updated version of the patchset for generic filesystem
events interface [1][2], hopefully handling issues raised during the previous
run.

Changes from v2:
	- Switched to kref for reference counting
	- Support for the events has been made optional (config option)
	- Use dynamically assigned id for multicast group instead of
	  using static one
	- Verify if there are any net listeners prior to sending the msg
	- Make the interface more namespace-aware (handling mount dropped
	  and showing the content of config file). As for the network
	  namespaces - as before only the init net namespace is being
	  supported.

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
[2] https://lkml.org/lkml/2015/4/27/244
---

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 |  232 ++++++++++
 fs/Kconfig                           |    2 +
 fs/Makefile                          |    1 +
 fs/events/Kconfig                    |    7 +
 fs/events/Makefile                   |    5 +
 fs/events/fs_event.c                 |  809 ++++++++++++++++++++++++++++++++++
 fs/events/fs_event.h                 |   22 +
 fs/events/fs_event_netlink.c         |  104 +++++
 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             |   72 +++
 include/uapi/linux/Kbuild            |    1 +
 include/uapi/linux/fs_event.h        |   58 +++
 mm/shmem.c                           |   33 +-
 21 files changed, 1419 insertions(+), 33 deletions(-)
 create mode 100644 Documentation/filesystems/events.txt
 create mode 100644 fs/events/Kconfig
 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

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2015-06-16 13:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 13:09 Beata Michalska [this message]
2015-06-16 13:09 ` [RFC v3 1/4] fs: Add generic file system event notifications Beata Michalska
     [not found]   ` <1434460173-18427-2-git-send-email-b.michalska-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-06-16 16:21     ` Al Viro
2015-06-17  9:22       ` Beata Michalska
2015-06-24  8:47     ` Dmitry Monakhov
2015-06-24 15:31       ` Beata Michalska
2015-06-24 16:26         ` Steve French
2015-06-26  7:30           ` Beata Michalska
2015-06-17 23:06   ` Dave Chinner
2015-06-18  8:25     ` Beata Michalska
2015-06-19  0:03       ` Dave Chinner
2015-06-19 17:28         ` Beata Michalska
2015-06-19 23:21           ` Dave Chinner
2015-06-22 15:46             ` Beata Michalska
2015-06-18 11:17   ` Kinglong Mee
2015-06-18 14:50     ` Beata Michalska
2015-07-22 15:55   ` Bartlomiej Zolnierkiewicz
2015-07-30  8:22     ` Beata Michalska
2015-06-16 13:09 ` [RFC v3 2/4] ext4: Add helper function to mark group as corrupted Beata Michalska
2015-07-22 10:40   ` Bartlomiej Zolnierkiewicz
     [not found] ` <1434460173-18427-1-git-send-email-b.michalska-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-06-16 13:09   ` [RFC v3 3/4] ext4: Add support for generic FS events Beata Michalska
2015-06-17  6:15     ` Leon Romanovsky
2015-06-17  9:25       ` Beata Michalska
2015-06-16 13:09 ` [RFC v3 4/4] shmem: " Beata Michalska
2015-06-17  6:08   ` Leon Romanovsky
2015-06-17  9:23     ` 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=1434460173-18427-1-git-send-email-b.michalska@samsung.com \
    --to=b.michalska@samsung.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=greg@kroah.com \
    --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).