From: Dmitry Monakhov <dmonakhov@openvz.org>
To: linux-fsdevel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, jack@suse.cz,
viro@ZenIV.linux.org.uk, adityakali@google.com,
Dmitry Monakhov <dmonakhov@openvz.org>
Subject: [PATCH 1/6] RFC: introduce extended inode owner identifier v8
Date: Sun, 2 Oct 2011 23:44:36 +0400 [thread overview]
Message-ID: <1317584681-29967-1-git-send-email-dmonakhov@openvz.org> (raw)
Hi, I've updated old standing project quota id patch-set.
Please take a look at it and replay me your opinion, especially if you
do not like it by some reason :) This is really important because i do
want this feature to be merged sooner or later.
*Feature description*
1) Inode may has a project identifier which has same meaning as uid/gid.
2) Id is stored in inode's xattr named "system.project_id"
3) Id is inherent from parent inode on creation.
4) This id is cached in memory fs_inode structure and may be accessible
via s_op->get_prjid(). This field it restricted by CONFIG_PROJECT_ID.
So no wasting of memory happens.
5) Since id is cached in memory it may be used for different purposes
such as:
5A) Implement additional quota id space orthogonal to uid/gid. This is
useful in managing quota for some filesystem hierarchy(chroot or
container over bindmount)
*User interface *
Project id is managed via generic xattr interface "system.project_id"
This good because
1) We may use already existing interface.
2) xattr already supported by generic utilities tar/rsync and etc
PATCH SET TOC:
1) generic projectid support
2) generic project quota support
3) ext4: small mount flags cleanup
4) ext4 project support implementation
4A) ext4: generic project support
4B) ext4: project quota support
Patch against 3.1.0-rc8-next-20110930
Actually vfs part is really small, and most changes happen in ext4-tree
Changes against V7
- Small fix for project switch error path
- Remove usless macro expressions
Changes against v6
- get rid of iattr stuff, current __dquot_transfer() provides sane interface
for quota manipulation. i_prjid can must be changed only by fs-speciffic
methods so only get() method is really necessery.
- remove #ifdef tricks from generic code.
- move i_prjid from vfs_inode to fs_inode, to prevent inode bloating.
- get rid of isolation logic, because this feature confuse most users.
Changes against v5
- convert dquota_transfer to struct iattr interface. Not it is possible
to change i_prjid via notify_changes()
- some bugfixes.
Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
next reply other threads:[~2011-10-02 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 19:44 Dmitry Monakhov [this message]
2011-10-02 19:44 ` [PATCH 2/6] Add additional owner identifier Dmitry Monakhov
2011-10-02 19:44 ` [PATCH 3/6] Implement project id support for generic quota Dmitry Monakhov
2011-10-02 19:44 ` [PATCH 4/6] ext4: get rid of didicated MOUNT_QUOTA option Dmitry Monakhov
2011-10-02 19:44 ` [PATCH 5/6] ext4: Implement project ID support for ext4 filesystem Dmitry Monakhov
2011-10-02 19:44 ` [PATCH 6/6] ext4: add project quota support 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=1317584681-29967-1-git-send-email-dmonakhov@openvz.org \
--to=dmonakhov@openvz.org \
--cc=adityakali@google.com \
--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).