From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 379F9C433FE for ; Sun, 9 Oct 2022 06:46:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229988AbiJIGqX (ORCPT ); Sun, 9 Oct 2022 02:46:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60742 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229968AbiJIGqD (ORCPT ); Sun, 9 Oct 2022 02:46:03 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D9F4332073 for ; Sat, 8 Oct 2022 23:45:39 -0700 (PDT) Received: from [2a02:8108:963f:de38:eca4:7d19:f9a2:22c5]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1ohQ3v-0005dm-5X; Sun, 09 Oct 2022 08:45:23 +0200 Message-ID: <021de720-4a57-1a88-f456-fcaeaa3653de@leemhuis.info> Date: Sun, 9 Oct 2022 08:45:22 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1 Subject: Re: BUG reproduced: 6.0.0-RC kernels trigger Firefox snap bug with 6.0.0-rc3 through 6.0.0-rc7 Content-Language: en-US, de-DE To: Mirsad Goran Todorovac , linux-kernel@vger.kernel.org Cc: Marc Miltenberger , "regressions@lists.linux.dev" , Slade Watkins References: <5bb75cbc-a0db-537b-12d0-889230c865d8@leemhuis.info> <0fb2a9ff-df76-8af9-e54a-c2dc6bfd9478@leemhuis.info> <6ba15505-1c04-df2b-237f-b3060f26d2e6@leemhuis.info> <25cd0e21-ed8e-1836-b0ec-c052c2276cd8@alu.unizg.hr> From: Thorsten Leemhuis In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1665297939;36b1353a; X-HE-SMSGID: 1ohQ3v-0005dm-5X Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08.10.22 18:43, Mirsad Goran Todorovac wrote: > On 08. 10. 2022. 15:41, Mirsad Goran Todorovac wrote: >> On 06. 10. 2022. 18:58, Thorsten Leemhuis wrote: >>> On 06.10.22 18:43, Mirsad Goran Todorovac wrote: >>>> On 06. 10. 2022. 15:23, Thorsten Leemhuis wrote: >>>>> On 06.10.22 14:43, Mirsad Todorovac wrote: >>>>>> On 10/6/22 14:25, Thorsten Leemhuis wrote: >>>>>> >>>>>>> One more question: >>>>>>> >>>>>>> On 06.10.22 14:00, Thorsten Leemhuis wrote: >>>>>>> Were those two vanilla kernels? I asked in #snappy on IRC and was >>>>>>> told >>>>>>> that "snapd simply expects some ubuntu bit in patched into the >>>>>>> kernel if >>>>>>> it detects that it runs on an official ubuntu install...". This >>>>>>> was also >>>>>>> suggested "it probably makes sense to file a but in LP to make the >>>>>>> kernel team aware". >>>>>> Yes, last time I tried it with git clone from linux_stable on >>>>>> kernel.org >>>>>> and >>>>>> config-6.0.0-060000-generic from the official Ubuntu mainline build >>>>> You don't want to do that. Better take the config used to build a >>>>> working kernel (say 5.19.y) and then build 6.0 with it (after running >>>>> "make olddefconfig"), because it might be a new kernel option (say >>>>> for a >>>>> new security technique) that might cause the problem, as explained >>>>> here: >>>>> https://docs.kernel.org/admin-guide/reporting-regressions.html >>>> If I understood well, that would mean building www.kernel.org git >>>> linux_stable >>>> source with Ubuntu's config-5.9.13-051903? >>> I meant "please download Linux 6.0 (ideally through git, that you have >>> everything to perform a bisection), add the config from a working kernel >>> (if config-5.9.13-051903 is one, yeah, then take that) as .config and >>> then run "make olddefconfig" before compiling and installing the kernel >>> to see if 6.0 fails with that config that was working. >> >> Having done this build with mentioned config-5.19.13-051903-config from >> Ubuntu's mainline build and your recommended make option >> had produced a kernel that so far did not exhibit the Firefox snap >> "tab crash/wrong Verneed record version" bug. >> >> However, the uptime is 1d 18h50min, so it might be too early to draw >> a definite general conclusion. >> >> Now, the brave conlusion seems to be that the culprit is one of the >> modules >> added in config-6.0.0-060000-generic. >> [...] A new module might be one possible explanation for such a situations, but there are others that are more likely. > I know that it is uncool to reply one's own email, No, it's not. At least not in the land of the Linux kernel. :-D > but this is new development: > > After starting a zoom spawned session, the Firefox snap tab crash > reappeared. > > I will reinstate that if was done with the config-5.19.13-generic and > "make olddefconfig" > followed by a "make -j 10 deb-pkg" build. > > Here is the exact log of my actions: > >   678  10/06/2022 06:44:58 PM  vi config-5.19.13-051913-generic >   679  10/06/2022 06:45:21 PM  time rm -rf linux_stable_build/ >   680  10/06/2022 06:45:31 PM  time cp -rp linux_stable linux_stable_build >   681  10/06/2022 06:46:39 PM  time diff -ur linux_stable linux_stable_build >   682  10/06/2022 06:47:38 PM  cp config-5.19.13-051913-generic > linux_stable_build/.config >   683  10/06/2022 06:47:46 PM  cd linux_stable_build >   684  10/06/2022 06:47:51 PM  make olddefconfig >   685  10/06/2022 06:48:05 PM  time nice make -j10 deb-pkg Yeah, then it's pretty certain that his is a regression. But it could be caused by all sorts of things and I have no idea where to start. We thus really could need a bisection to find the root of the problem. This will be hard, as this crash only happens infrequently. Thing is: the Ubuntu developers likely have a strong interest in this particular issue and due to their knowledge of snap have way better chances to pin-point the root case quickly. So submitting a bug report to them might be the best way forward in this situation, even if the kernel is likely at fault here. Ciao, Thorsten