[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB3wodeqmuE0iZeSddWSGuJ49rKUjSPb9xxsx189hdL9aMn_pQ@mail.gmail.com>
Date: Mon, 17 Oct 2022 18:25:35 +0100
From: Phillip Lougher <phillip.lougher@...il.com>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: Phillip Lougher <phillip@...ashfs.org.uk>,
regressions@...mhuis.info, mirsad.todorovac@....unizg.hr,
linux-kernel@...r.kernel.org, marcmiltenberger@...il.com,
regressions@...ts.linux.dev, srw@...dewatkins.net
Subject: Re: BISECT result: 6.0.0-RC kernels trigger Firefox snap bug with
6.0.0-rc3 through 6.0.0-rc7
On Mon, Oct 17, 2022 at 1:37 PM Bagas Sanjaya <bagasdotme@...il.com> wrote:
>
> On 10/17/22 16:45, Bagas Sanjaya wrote:
> > On 10/16/22 19:21, Bagas Sanjaya wrote:
> >>
> >> No Verneed warnings so far. However, I need to test for a longer time
> >> (a day) to check if any warnings are reported.
> >>
> >
> > The regression still occurs with this patch applied. Let's see if
> > reverting the offending commit helps.
> >
> Sorry for speaking late about my triggering cause.
>
> As the background, on my Debian 11 computer, I have lxd snap installed.
> I use lxd to channel my sysadmin side by spinning up containers and
> installing server applications there (LAMP, email, DNS).
>
> Back to triggering cause. I can trigger the regression when the network
> connection drops (when Firefox shows connection problem page). Then
> I run `lxd list` to list container instances and I get the Verneed
> regression error.
>
This appears to be both deterministic, and appears to show something
happening in the Firefox snap triggers an error in the Lxd snap.
This will then not be a Squashfs issue. Firefox running in one
Squashfs filesystem
can't trigger a failure in another Squashfs filesystem. This has to be caused
by something else.
Thanks
Phillip
Powered by blists - more mailing lists