linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: linux-fsdevel@vger.kernel.org
Cc: Dmitry Monakhov <dmonakhov@openvz.org>
Subject: [PATCH 3/6] vfs: Add additional owner identifier
Date: Thu, 18 Feb 2010 19:45:27 +0300	[thread overview]
Message-ID: <1266511530-10533-4-git-send-email-dmonakhov@openvz.org> (raw)
In-Reply-To: <1266511530-10533-3-git-send-email-dmonakhov@openvz.org>


Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
---
 fs/Kconfig            |    7 +++++++
 include/linux/fs.h    |    5 +++++
 include/linux/xattr.h |    3 +++
 3 files changed, 15 insertions(+), 0 deletions(-)

diff --git a/fs/Kconfig b/fs/Kconfig
index 64d44ef..ad47589 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -54,6 +54,13 @@ config FILE_LOCKING
 	  This option enables standard file locking support, required
           for filesystems like NFS and for the flock() system
           call. Disabling this option saves about 11k.
+config METAGROUP
+	bool "Enable metagroup inode identifier"
+	default y
+	help
+	  This option enables metagroup inode identifier. Metagroup
+	  may be used as auxiliary owner specifier in addition to
+	  standard uid/gid.
 
 source "fs/notify/Kconfig"
 
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 0cd0105..f1139ed 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1586,6 +1586,11 @@ struct aux_attributes
 	 * and protected by i_lock similar to i_blocks+i_bytes. */
 	qsize_t* (*reserved_space)(struct inode *inode);
 #endif
+#ifdef CONFIG_METAGROUP
+	/* Metagroup id, protected by i_mutex similar to i_uid/i_gid*/
+	uid_t* (*metagroup)(struct inode *inode);
+#endif
+
 };
 /*
  * Inode state bits.  Protected by inode_lock.
diff --git a/include/linux/xattr.h b/include/linux/xattr.h
index fb9b7e6..efd9ed1 100644
--- a/include/linux/xattr.h
+++ b/include/linux/xattr.h
@@ -33,6 +33,9 @@
 #define XATTR_USER_PREFIX "user."
 #define XATTR_USER_PREFIX_LEN (sizeof (XATTR_USER_PREFIX) - 1)
 
+#define XATTR_METAGROUP "system.metagroup"
+#define XATTR_METAGROUP_LEN (sizeof (XATTR_METAGROUP))
+
 struct inode;
 struct dentry;
 
-- 
1.6.6


  reply	other threads:[~2010-02-18 16:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 16:45 [PATCH 0/6] RFC: introduce extended inode owner identifier v4 Dmitry Monakhov
2010-02-18 16:45 ` [PATCH 1/6] vfs: add per-sb auxiliary inode attribute table Dmitry Monakhov
2010-02-18 16:45   ` [PATCH 2/6] quota: switch reservation space management to aux_attribute Dmitry Monakhov
2010-02-18 16:45     ` Dmitry Monakhov [this message]
2010-02-18 16:45       ` [PATCH 4/6] quota: Implement metagroup support for quota Dmitry Monakhov
2010-02-18 16:45         ` [PATCH 5/6] ext4: enlarge mount option field Dmitry Monakhov
2010-02-18 16:45           ` [PATCH 6/6] ext4: Implement metagroup support for ext4 filesystem Dmitry Monakhov
2010-02-18 19:00   ` [PATCH 1/6] vfs: add per-sb auxiliary inode attribute table Brad Boyer
2010-02-18 19:34     ` Dmitry Monakhov
2010-02-18 23:31 ` [PATCH 0/6] RFC: introduce extended inode owner identifier v4 Dave Chinner
2010-02-19 10:16   ` Dmitry Monakhov
2010-02-19 23:31     ` Dave Chinner
2010-02-20 10:58       ` Dmitry Monakhov

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=1266511530-10533-4-git-send-email-dmonakhov@openvz.org \
    --to=dmonakhov@openvz.org \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).