From: Chris Murphy <email@example.com>
To: Amir Goldstein <firstname.lastname@example.org>
Cc: Chris Murphy <email@example.com>,
Miklos Szeredi <firstname.lastname@example.org>,
Subject: Re: btrfs+overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off.
Date: Sun, 11 Apr 2021 00:05:20 -0600 [thread overview]
Message-ID: <CAJCQCtSzENaFsZ_mcDv8OANDmpbUWoo+u1RVgfZ=hpxK5hQ7bg@mail.gmail.com> (raw)
On Sat, Apr 10, 2021 at 11:12 PM Amir Goldstein <email@example.com> wrote:
> Now I'm confused again.
So am I, and in retrospect I've posted here prematurely.
> Your reports starts by stating:
> "The primary problem is Bolt (Thunderbolt 3) tests that are
> experiencing a regression when run in a container using overlayfs,"
> But you say that the problem exists with kernel 5.9.
> When you say "regression" above, what are you referring to?
Overlayfs. Now that I've tested 5.9, I'm not so sure it's a kernel regression.
> Did those tests pass in a previous Bolt version?
> Did those tests ever pass in a container using overlayfs?
Yes and yes.
> There is surely a bug in overlayfs, but it's hard to find it without
> minimal bisection info. I'll keep looking.
> If it's a regression with newer distro, please try to understand
> from distro/package managers, what has changed in the container
> setup and kernel config w.r.t a container using overlayfs.
Exactly. The original report of the problem is Alpine linux, but I
can't reproduce it on Fedora except with podman using an Alpine image
base. As all the other suspects have fallen apart, what remains
untested for regressions is this.
next prev parent reply other threads:[~2021-04-11 6:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 22:03 btrfs+overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off Chris Murphy
2021-04-10 8:03 ` Amir Goldstein
2021-04-10 17:36 ` Chris Murphy
2021-04-10 17:55 ` Amir Goldstein
2021-04-10 19:36 ` Chris Murphy
2021-04-10 19:42 ` Chris Murphy
2021-04-10 19:43 ` Chris Murphy
2021-04-10 19:44 ` Chris Murphy
2021-04-10 20:03 ` Chris Murphy
2021-04-11 5:12 ` Amir Goldstein
2021-04-11 6:05 ` Chris Murphy [this message]
2021-04-11 7:28 ` Amir Goldstein
2021-04-13 21:50 ` Chris Murphy
2021-04-12 8:41 ` Miklos Szeredi
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).