From: Dmitry Monakhov <dmonakhov@openvz.org>
To: linux-fsdevel@vger.kernel.org
Cc: viro@ZenIV.linux.org.uk, jack@suse.cz,
linux-ext4@vger.kernel.org,
Dmitry Monakhov <dmonakhov@openvz.org>
Subject: [PATCH 1/4] vfs: Add additional owner identifier
Date: Fri, 29 Oct 2010 17:03:37 +0400 [thread overview]
Message-ID: <1288357420-7178-2-git-send-email-dmonakhov@openvz.org> (raw)
In-Reply-To: <1288357420-7178-1-git-send-email-dmonakhov@openvz.org>
This patch add project inode identifier. Project ID may be used as
auxiliary owner specifier in addition to standard uid/gid.
Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
---
fs/Kconfig | 7 +++++++
include/linux/fs.h | 1 +
include/linux/xattr.h | 3 +++
3 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/fs/Kconfig b/fs/Kconfig
index c49e224..4250f0b 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -58,6 +58,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 PROJECT_ID
+ bool "Enable project inode identifier"
+ default y
+ help
+ This option enables project inode identifier. Project ID
+ 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 24dd5d5..cba9a65 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1611,6 +1611,7 @@ struct super_operations {
#endif
int (*bdev_try_to_free_page)(struct super_block*, struct page*, gfp_t);
int (*trim_fs) (struct super_block *, struct fstrim_range *);
+ u32 (*get_prjid)(const struct inode *inode);
};
/*
diff --git a/include/linux/xattr.h b/include/linux/xattr.h
index f1e5bde..2f64a1c 100644
--- a/include/linux/xattr.h
+++ b/include/linux/xattr.h
@@ -47,6 +47,9 @@
#define XATTR_CAPS_SUFFIX "capability"
#define XATTR_NAME_CAPS XATTR_SECURITY_PREFIX XATTR_CAPS_SUFFIX
+#define XATTR_PRJID "system.project_id"
+#define XATTR_PRJID_LEN (sizeof (XATTR_PRJID))
+
struct inode;
struct dentry;
--
1.6.5.2
next prev parent reply other threads:[~2010-10-29 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 13:03 [PATCH 0/4] RFC: introduce extended inode owner identifier v7 Dmitry Monakhov
2010-10-29 13:03 ` Dmitry Monakhov [this message]
2010-10-29 13:03 ` [PATCH 2/4] quota: Implement project id support for generic quota Dmitry Monakhov
2010-10-29 13:03 ` [PATCH 3/4] ext4: Implement project ID support for ext4 filesystem Dmitry Monakhov
2010-10-29 13:03 ` [PATCH 4/4] ext4: add project quota support Dmitry Monakhov
2010-11-19 5:51 ` Ping [PATCH 0/4] RFC: introduce extended inode owner identifier v7 Dmitry
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=1288357420-7178-2-git-send-email-dmonakhov@openvz.org \
--to=dmonakhov@openvz.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).