From: hujianyang <hujianyang@huawei.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Seunghun Lee <waydi1@gmail.com>, linux-unionfs@vger.kernel.org
Subject: Re: Allow non-workdir mount in overlayfs?
Date: Wed, 14 Jan 2015 18:18:35 +0800 [thread overview]
Message-ID: <54B6427B.6010908@huawei.com> (raw)
In-Reply-To: <CAJfpegsCdRkw6unNM5txd8ZJvvw-X=v_LEw=iMVUvDPox1O_EA@mail.gmail.com>
On 2015/1/14 17:55, Miklos Szeredi wrote:
> On Wed, Jan 14, 2015 at 3:45 AM, hujianyang <hujianyang@huawei.com> wrote:
>> Hi Miklos,
>>
>> I was considering the "FIXME: workdir is not needed for a R/O mount"
>> you left in ovl_fill_super() these days.
>>
>> Actually Seunghun (Seunghun Lee <waydi1@gmail.com>) has sent a patch
>> about these problem. But I have some different ideas. I think there are
>> two ways to fix this problem. One, just remove this *FIXME*. Another,
>> Allow non-workdir mount.
>>
>> 1) Remove *FIXME*; Further, use workdir in R/W case only
>>
>> As multi-layer mount are allowed in ovl, users could initialize a R/O
>> mount by setting multi lower directories. Workdir should only be used
>> in R/W case with upperdir exist. So this *FIXME* can be removed.
>>
>> We should add some information in the code and document about this.
>
> I'd vote for this.
>
> If there's no workdir, just use multiple lowedirs.
>
> If there is a workdir, then specify it (and overlay can still be
> mounted R/O, possibly remounted R/W)
>
Got it~!
I'd like to send a patch about it tomorrow.
By the way, I think we should add a error message in parse_opt,
see the mail send by Fabian, do you agree with it?
Thanks,
Hu
prev parent reply other threads:[~2015-01-14 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 2:45 Allow non-workdir mount in overlayfs? hujianyang
2015-01-14 9:55 ` Miklos Szeredi
2015-01-14 10:18 ` hujianyang [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=54B6427B.6010908@huawei.com \
--to=hujianyang@huawei.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=waydi1@gmail.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