linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. R. Okajima" <hooanon05@yahoo.co.jp>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Alessandro Pignotti <alexpigna.dev@gmail.com>,
	Linux-Fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [Patch] Support overriding uid/gid in overlayfs
Date: Fri, 01 Feb 2013 13:45:34 +0900	[thread overview]
Message-ID: <7500.1359693934@jrobl> (raw)
In-Reply-To: <CAJfpegt4=BBXM4rGzT6WqSZUhn8vLjbFU0mPHUSkysL9_VQTWA@mail.gmail.com>


Miklos Szeredi:
> They don't "solve" this, it's a fundamental property of the
> implementation.  Overlayfs and union-mounts behave as if copy-up was a
> "bind mount" over the file in question.  Yes, it's a namespace trick
> but it seems to work in most situations.

It must be a sad news for overlayfs users who have every met "non-most"
situations.


> The point was that uid/gid was to be overridden with *different*
> values for each overlayfs instance.  So implementing uid/gid
> overriding in the lower fs doesn't help.

For the scenario which Alessandro Pignotti posted,
- everything on the lower fs are owned by a single user, by the
  overriding feature.
- everything on the upper fs are owned by the user natively.
Isn't it enough?


J. R. Okajima

      reply	other threads:[~2013-02-01  4:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1358254695.3380.16.camel@avalon>
2013-01-25 11:08 ` [Patch] Support overriding uid/gid in overlayfs Miklos Szeredi
2013-01-28 15:58   ` Alessandro Pignotti
2013-01-31 16:15     ` Miklos Szeredi
2013-01-31 17:01       ` J. R. Okajima
2013-01-31 17:40         ` Miklos Szeredi
2013-02-01  4:45           ` J. R. Okajima [this message]

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=7500.1359693934@jrobl \
    --to=hooanon05@yahoo.co.jp \
    --cc=alexpigna.dev@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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).