linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] vfs generic subtree support
Date: Tue, 16 Feb 2010 14:21:54 +0000	[thread overview]
Message-ID: <20100216142154.GE30031@ZenIV.linux.org.uk> (raw)
In-Reply-To: <87mxz9nutb.fsf@openvz.org>

On Tue, Feb 16, 2010 at 05:01:36PM +0300, Dmitry Monakhov wrote:

> Let's call it "metagroup" id. If you know better (more descriptive) word
> for this purpose i please make your suggestion.
> 
> - Such metagroup may be assigned to inode. And this id is stored on
>   inode.
> - It may be inherent from parent, if corresponding flag is set 
>   on parent dir.
> - metagroup id may be used by generic quota.

I would probably like to see example with fewer "may" and more details ;-)
Seriously, what kind of rules and uses for it do you have in mind?  More
specific example would be nice...

  reply	other threads:[~2010-02-16 14:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16 10:52 [RFC] vfs generic subtree support Dmitry Monakhov
2010-02-16 12:20 ` Al Viro
2010-02-16 12:37   ` Dmitry Monakhov
2010-02-16 13:38     ` Al Viro
2010-02-16 14:01       ` Dmitry Monakhov
2010-02-16 14:21         ` Al Viro [this message]
2010-02-16 15:00           ` Dmitry Monakhov
2010-02-16 15:12             ` Matthew Wilcox
2010-02-16 15:32               ` Dmitry Monakhov
2010-02-16 19:25                 ` J. Bruce Fields
2010-02-16 19:32                   ` Christoph Hellwig
2010-02-16 19:39                     ` J. Bruce Fields

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=20100216142154.GE30031@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=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).