From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jingbo Xu <jefflexu@linux.alibaba.com>,
Miklos Szeredi <miklos@szeredi.hu>,
overlayfs <linux-unionfs@vger.kernel.org>,
Xiang Gao <xiang@kernel.org>, "zhangyi (F)" <yi.zhang@huawei.com>,
kmxz <kxzkxz7139@gmail.com>
Subject: Re: [potential issue, question] whiteout shows up in merged directory
Date: Mon, 4 Sep 2023 23:12:50 +0800 [thread overview]
Message-ID: <bc9b3731-9eac-28be-e635-44a098e87d76@linux.alibaba.com> (raw)
In-Reply-To: <CAOQ4uxgiBNcD-vBi3OLF5Nc8gHYS-Hm1=yA4+At=nRUk18A9ng@mail.gmail.com>
On 2023/9/4 23:03, Amir Goldstein wrote:
> On Mon, Sep 4, 2023 at 5:38 PM Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
..
>>>>
>>>
>>> Let me put it this way:
>>> If there was an official offline tool to merge overlayfs layers
>>> I would expect that tool to mark the offline merged directories
>>> with an empty "trusted.overlayfs.origin", to be able to distinguish
>>> them from pure non-merge directories.
>>>
>>> I do not consider dealing with this in erofs-utils side a workaround
>>> I consider it crafting layers in expected overlayfs format.
>>
>> Thanks for the hints.
>>
>> Ok, marking impure makes sense as long as it's properly described.
>>
>> Just tried to describe the background since the question I think
>> is not quite erofs-utils specific, btw, if there could be some
>> reference official offline tool, that would be great!
>>
>
> There is this tool from kmxz that supports offline merge:
> https://github.com/kmxz/overlayfs-tools
> but it is not in any way "official".
>
> I have contributed redirect and metacopy support in 2020
> and there hasn't been much traffic since.
> This tool does not deal with origin and impure xattrs.
Thanks, very useful link! will also check this later.
>
> Thanks,
> Amir.
next prev parent reply other threads:[~2023-09-04 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 7:47 [potential issue, question] whiteout shows up in merged directory Jingbo Xu
2023-09-04 8:57 ` Amir Goldstein
2023-09-04 12:49 ` Jingbo Xu
2023-09-04 13:27 ` Gao Xiang
2023-09-04 14:07 ` Amir Goldstein
2023-09-04 14:38 ` Gao Xiang
2023-09-04 15:03 ` Amir Goldstein
2023-09-04 15:12 ` Gao Xiang [this message]
2023-09-04 15:01 ` Jingbo Xu
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=bc9b3731-9eac-28be-e635-44a098e87d76@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=amir73il@gmail.com \
--cc=jefflexu@linux.alibaba.com \
--cc=kxzkxz7139@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=xiang@kernel.org \
--cc=yi.zhang@huawei.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