From: Christian Brauner <christian.brauner@ubuntu.com>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
Miklos Szeredi <mszeredi@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: overlayfs regression
Date: Thu, 25 Jun 2020 15:21:59 +0200 [thread overview]
Message-ID: <20200625132159.splbwlxadteukah6@wittgenstein> (raw)
In-Reply-To: <20200625131943.GX14915@ubuntu-x1>
On Thu, Jun 25, 2020 at 08:19:43AM -0500, Seth Forshee wrote:
> On Wed, Jun 24, 2020 at 07:24:24PM +0300, Amir Goldstein wrote:
> > On Wed, Jun 24, 2020 at 6:35 PM Christian Brauner
> > <christian.brauner@ubuntu.com> wrote:
> > >
> > > On Wed, Jun 24, 2020 at 06:25:55PM +0300, Amir Goldstein wrote:
> > > > On Wed, Jun 24, 2020 at 5:48 PM Christian Brauner
> > > > <christian.brauner@ubuntu.com> wrote:
> > > > >
> > > > > Hey Miklosz,
> > > > > hey Amir,
> > > > >
> > > > > We've been observing regressions in our containers test-suite with
> > > > > commit:
> > > > >
> > > > > Author: Miklos Szeredi <mszeredi@redhat.com>
> > > > > Date: Tue Mar 17 15:04:22 2020 +0100
> > > > >
> > > > > ovl: separate detection of remote upper layer from stacked overlay
> > > > >
> > > > > Following patch will allow remote as upper layer, but not overlay stacked
> > > > > on upper layer. Separate the two concepts.
> > > > >
> > > > > This patch is doesn't change behavior.
> > > > >
> > > > > Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
> > > > >
> > > >
> > > > Are you sure this is the offending commit?
> > > > Look at it. It is really moving a bit of code around and should not
> > > > change logic.
> > > > There are several other commits in 5.7 that could have gone wrong...
> > >
> > > Yeah, most likely. I can do a bisect but it might take a little until I
> > > get around to it. Is that ok?
> > >
> >
> > ok.
> > I thought you pointed to a commit that you bisected the regression to.
> > I guess not.
>
> I think this is only an Ubuntu problem, it looks like someone did some
> bad conflict resoluation when rebasing a sauce patch onto 5.7.
Yeah, I just saw this as well.
Sorry for the noise.
Christian
prev parent reply other threads:[~2020-06-25 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 14:48 overlayfs regression Christian Brauner
2020-06-24 15:25 ` Amir Goldstein
2020-06-24 15:35 ` Christian Brauner
2020-06-24 16:24 ` Amir Goldstein
2020-06-25 13:19 ` Seth Forshee
2020-06-25 13:21 ` Christian Brauner [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=20200625132159.splbwlxadteukah6@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=seth.forshee@canonical.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;
as well as URLs for NNTP newsgroup(s).