From: Miklos Szeredi <miklos@szeredi.hu>
To: Alessandro Pignotti <alexpigna.dev@gmail.com>
Cc: Linux-Fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [Patch] Support overriding uid/gid in overlayfs
Date: Thu, 31 Jan 2013 17:15:19 +0100 [thread overview]
Message-ID: <CAJfpegtYpbBoErC22f1bJQrr_ZZQpredan89DckusBXDoCk6Xw@mail.gmail.com> (raw)
In-Reply-To: <1359388685.2499.16.camel@avalon>
On Mon, Jan 28, 2013 at 4:58 PM, Alessandro Pignotti
<alexpigna.dev@gmail.com> wrote:
> Hi everyone,
>
> the proposed patch would be useful in the following scenario
>
> 1) There is a large directory tree which needs to be fully read/write
> accessible from many different users, although in an isolated way (i.d.
> the changes made by Alice should not be visible to Bob)
> 2) All users expect to be owning the files. (i.d. that everything is
> private)
>
> With the proposed patch it is possible to store a single copy of the
> base directory tree and use it as the lowerdir. The upperdir is then set
> to a private user-writable directory. Each user as the illusion of a
> private fully-writable installation as required. Moreover, since all the
> changed files ends up in the upperdir it's easy to pack them for backup
> purposes.
Okay, makes sense.
One issue, though, is that stat("x") and fd=open("x"); fstat(fd) will
return different file stats (the fstat one will return the stats for
the original file). This may confuse some apps.
This is a something a "true" union filesystem can do better that
union-mounts or overlayfs.
Thanks,
Miklos
next prev parent reply other threads:[~2013-01-31 16:15 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 [this message]
2013-01-31 17:01 ` J. R. Okajima
2013-01-31 17:40 ` Miklos Szeredi
2013-02-01 4:45 ` J. R. Okajima
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=CAJfpegtYpbBoErC22f1bJQrr_ZZQpredan89DckusBXDoCk6Xw@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=alexpigna.dev@gmail.com \
--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).