linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: 王元良 <yuanliang.wyl@alibaba-inc.com>
Cc: "adilger.kernel" <adilger.kernel@dilger.ca>,
	pkuelelixi <pkuelelixi@gmail.com>, jack <jack@suse.cz>,
	linux-ext4 <linux-ext4@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext4, quota, projectid:  limits without capablity
Date: Fri, 5 Jan 2018 14:20:20 -0500	[thread overview]
Message-ID: <20180105192020.GB8287@thunk.org> (raw)
In-Reply-To: <c18ff577-be92-40ea-93ae-4401ce2107da.yuanliang.wyl@alibaba-inc.com>

On Fri, Jan 05, 2018 at 03:23:43PM +0800, 王元良 wrote:
> 
> hi,  all
> We use projectid for space restrictions inside the container, share the same hard link between the host and multiple containers.
> But I encountered a problem, as follows, are the following modifications feasible ?

I'm not sure what the problem that you encoutered.  So it's hard to
judge the modification, especially since you didn't send it in a
proper unified diff format.

It looks like you are trying to allow root to avoid the restriction an
entire directory hierarchy (all files and subdirectories) must have
the same project ID.  There are a couple of problems with this.  For
example, you only do this for the link case, but we enforce the same
restriction in other places, such as the rename case.

The current restrictions are to make life simpler for users.  The
restrictions are also part of the xfstests regression test, so I'm
fairly certain will cause a test failure.

So this is something I wouldn't want to do without general agreement
across all of the file systems developers, since it breaks the
fundamental model of how project IDs are presented to users, and could
end up making things extremely confusing.  So the best way to do this
is for you to give much more details about why you want this change,
and what is the larger context of what is you are trying to do.

    	    	       	       	  - Ted

       reply	other threads:[~2018-01-05 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c18ff577-be92-40ea-93ae-4401ce2107da.yuanliang.wyl@alibaba-inc.com>
2018-01-05 19:20 ` Theodore Ts'o [this message]
     [not found] ` <0dc571a8-e1b2-4247-9e9d-df02c0b0d7c6.yuanliang.wyl@alibaba-inc.com>
2018-01-10 11:59   ` 回复:ext4, quota, projectid: limits without capablity Jan Kara

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=20180105192020.GB8287@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pkuelelixi@gmail.com \
    --cc=yuanliang.wyl@alibaba-inc.com \
    /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).