From: Alexander Larsson <alexl@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>,
Miklos Szeredi <mszeredi@redhat.com>
Cc: linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] ovl: require xwhiteout feature flag on layer roots
Date: Fri, 19 Jan 2024 17:35:47 +0100 [thread overview]
Message-ID: <5ee3a210f8f4fc89cb750b3d1a378a0ff0187c9f.camel@redhat.com> (raw)
In-Reply-To: <CAOQ4uxiWtdgCQ+kBJemAYbwNR46ogP7DhjD29cqAw0qqLvQn4A@mail.gmail.com>
On Fri, 2024-01-19 at 13:08 +0200, Amir Goldstein wrote:
> On Fri, Jan 19, 2024 at 12:14 PM Miklos Szeredi <mszeredi@redhat.com>
> wrote:
>
>
> Do you want me to fix/test and send this to Linus?
>
> Alex, can we add your RVB to v2?
I ran into an issue converting composefs to use this.
Suppose we have a chroot of files containing some upper dirs and we
want to make a composefs of this. For example, say
/foo/lower/dir/whiteout is a traditional whiteout.
Previously, what happened is that I marked the whiteout file with
trusted.overlay.overlay.whiteout, and the /foo/lower/dir with
trusted.overlay.overlay.whiteouts.
Them when I mounted then entire chroot with overlayfs these xattrs
would get unescaped and I would get a $mnt/foo/lower/dir/whiteout with
a trusted.overlay.whiteout xattr, and a $mnt/foo/lower/dir with a
trusted.overlay.whiteout. When I then mounted another overlayfs with a
lowerdir of $mnt/foo/lower it would treat the whiteout as a xwhiteout.
However, now I need the lowerdir toplevel dir to also have a
trusted.overlay.whiteouts xattr. But when I'm converting the entire
chroot I do not know which of the directories is going to be used as
the toplevel lower dir, so I don't know where to put this marker.
The only solution I see is to put it on *all* parent directories. Is
there a better approach here?
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
=-=-=
Alexander Larsson Red Hat,
Inc
alexl@redhat.com alexander.larsson@gmail.com
He's a scrappy day-dreaming inventor looking for a cure to the poison
coursing through his veins. She's a foxy snooty stripper with someone
else's memories. They fight crime!
next prev parent reply other threads:[~2024-01-19 16:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 10:14 [PATCH v2] ovl: require xwhiteout feature flag on layer roots Miklos Szeredi
2024-01-19 11:08 ` Amir Goldstein
2024-01-19 11:20 ` Miklos Szeredi
2024-01-19 12:19 ` Amir Goldstein
2024-01-19 12:29 ` Alexander Larsson
2024-01-19 14:12 ` Amir Goldstein
2024-01-19 16:35 ` Alexander Larsson [this message]
2024-01-19 19:06 ` Amir Goldstein
2024-01-19 20:29 ` Miklos Szeredi
2024-01-20 10:32 ` Amir Goldstein
2024-01-22 10:01 ` Alexander Larsson
2024-01-22 8:38 ` Amir Goldstein
2024-01-22 10:44 ` Alexander Larsson
2024-01-22 11:30 ` Amir Goldstein
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=5ee3a210f8f4fc89cb750b3d1a378a0ff0187c9f.camel@redhat.com \
--to=alexl@redhat.com \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=stable@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).