From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem
Date: Thu, 11 Mar 2010 16:30:51 +0300 [thread overview]
Message-ID: <877hpjj88k.fsf@openvz.org> (raw)
In-Reply-To: <20100311120623.GC4706@infradead.org> (Christoph Hellwig's message of "Thu, 11 Mar 2010 07:06:23 -0500")
Christoph Hellwig <hch@infradead.org> writes:
> On Thu, Mar 04, 2010 at 09:34:35PM +0300, Dmitry Monakhov wrote:
>> Project id is stored on disk inside xattr usually inside ibody.
>> Xattr is used only as a data storage, It has not user visible xattr
>> interface.
>>
>> * User interface
>> Project id is accessible via generic xattr interface "system.project_id"
>>
>> TODO: implement e2libfs support for project_id.
>
> I think you'd be much better off storing it inide the inode core itself.
> E.g. you could ue the never used fragment address in the ext2/3/4 disk
> inode.http://patchwork.ozlabs.org/patch/38766
This was already discussed at the first RFC
http://patchwork.ozlabs.org/patch/38766
and Andreas was strongly against this idea.
>
>> +#ifdef CONFIG_QUOTA
>> + qid[PRJQUOTA] = new_prjid;
>> + ret = inode->i_sb->dq_op->transfer(inode, qid, 1 << PRJQUOTA);
>> + if (ret)
>> + return ret;
>> +#endif
>
> This needs to be updated to use dquot_transfer directly.
next prev parent reply other threads:[~2010-03-11 13:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 18:34 [PATCH 0/5] RFC: introduce extended inode owner identifier v5 Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 1/5] vfs: Add additional owner identifier Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 2/5] quota: Implement project id support for generic quota Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 4/5] ext4: add isolated project support Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 5/5] ext4: add project quota support Dmitry Monakhov
2010-03-04 20:07 ` [PATCH 4/5] ext4: add isolated project support Jan Kara
2010-03-04 20:34 ` Dmitry Monakhov
2010-03-11 12:07 ` Christoph Hellwig
2010-03-11 12:06 ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Christoph Hellwig
2010-03-11 13:30 ` Dmitry Monakhov [this message]
2010-03-11 19:54 ` Andreas Dilger
2010-03-11 22:01 ` tytso
2010-03-12 9:32 ` Dmitry Monakhov
2010-03-12 20:07 ` J. Bruce Fields
2010-03-11 12:03 ` [PATCH 2/5] quota: Implement project id support for generic quota Christoph Hellwig
2010-03-11 13:17 ` Dmitry Monakhov
2010-03-11 12:01 ` [PATCH 1/5] vfs: Add additional owner identifier Christoph Hellwig
2010-03-11 13:11 ` Dmitry Monakhov
2010-03-11 18:51 ` J. Bruce Fields
2010-03-11 19:40 ` Andreas Dilger
2010-03-12 8:47 ` Dmitry Monakhov
-- strict thread matches above, loose matches on Subject: below --
2010-03-18 14:02 [PATCH 0/5] RFC: introduce extended inode owner identifier v6 Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 1/5] vfs: Add additional owner identifier Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 2/5] quota: Implement project id support for generic quota Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Dmitry Monakhov
2010-03-18 21:25 ` Andreas Dilger
2010-03-19 8:16 ` Dmitry Monakhov
2012-06-21 9:08 [PATCH 0/5] RFC: introduce extended inode owner identifier v9 Dmitry Monakhov
2012-06-21 9:08 ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Dmitry Monakhov
2012-06-21 23:51 ` Jan Kara
2012-07-03 18:46 ` Dmitry Monakhov
2012-06-22 3:07 ` Dave Chinner
2012-06-28 10:16 ` Jan Kara
2012-07-03 19:11 ` 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=877hpjj88k.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.