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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 58D19C4338F for ; Sat, 7 Aug 2021 23:20:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3728561050 for ; Sat, 7 Aug 2021 23:20:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229904AbhHGXU6 (ORCPT ); Sat, 7 Aug 2021 19:20:58 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:34213 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229797AbhHGXU5 (ORCPT ); Sat, 7 Aug 2021 19:20:57 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id DAA295C00EE; Sat, 7 Aug 2021 19:20:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sat, 07 Aug 2021 19:20:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=C2Kr+e Eh5+xzHcKB01XFOXm7GGyi4YjtCJ20uK8zVjw=; b=M6P9BUvJeg/pne9wVqPnuR qFXn7X0S2HLePU6EkRDnRngSGlqs46ZE1rRa3o96umGb4JHhnoYUkV3tGt9kDg5t 4eGlRWMkLbEdLA2G9ZvITB62hPfJKOLp6l+XO40ACZhVQS1hgb8bo+zQgnntK8js t6eagLpw7kdtvYYiWEE0zTBcJUT2qh90xpMOzH9GmXfQ4TIScMDLiU1GT1GFri7j OuKz8vTvb51n0WhovuGyKoMDVJOLmo//xMxgJfI4AQnuE1pfA7FeiJVGy5W08X6Y JjCtkVrP8oFrj8U4K1f2pIBfFu8WztDBROz/kFL8Cp58OII0MbBmo5wqY57Oa+BA == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrjeeggdduvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvufgjkfhfgggtsehttdertddttddvnecuhfhrohhmpefhihhnnhcuvfhh rghinhcuoehfthhhrghinheslhhinhhugidqmheikehkrdhorhhgqeenucggtffrrghtth gvrhhnpeekgeejkeffhfefgeelieffueethfeludduhfdtteduvddthedtteeftdevfefh jeenucffohhmrghinhepudegqdhrtgdurdhishenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehfthhhrghinheslhhinhhugidqmheikehkrdho rhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 7 Aug 2021 19:20:35 -0400 (EDT) Date: Sun, 8 Aug 2021 09:19:54 +1000 (AEST) From: Finn Thain To: Mikael Pettersson cc: Linux Kernel list , linux-m68k@lists.linux-m68k.org, stable@vger.kernel.org Subject: Re: [BISECTED][REGRESSION] 5.10.56 longterm kernel breakage on m68k/aranym In-Reply-To: Message-ID: <31298797-f791-4ac5-cfda-c95d7c7958a4@linux-m68k.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 7 Aug 2021, Mikael Pettersson wrote: > I updated the 5.10 longterm kernel on one of my m68k/aranym VMs from > 5.10.47 to 5.10.56, and the new kernel failed to boot: > > ARAnyM 1.1.0 > Using config file: 'aranym1.headless.config' > Could not open joystick 0 > ARAnyM RTC Timer: /dev/rtc: Permission denied > ARAnyM LILO: Error loading ramdisk 'root.bin' > Blitter tried to read byte from register ff8a00 at 0077ee > > At this point it kept running, but produced no output to the console, > and would never get to the point of starting user-space. Attaching gdb > to aranym showed nothing interesting, i.e. it seemed to be executing > normally. > > A git bisect identified the following commit between 5.10.52 and > 5.10.53 as the culprit: > # first bad commit: [9e1cf2d1ed37c934c9935f2c0b2f8b15d9355654] > mm/userfaultfd: fix uffd-wp special cases for fork() > That commit appeared in mainline between v5.13 and v5.14-rc1. Is mainline also affected? e.g. v5.14-rc4. > 5.10.52, 5.11.22, 5.12.19, and 5.13.8 all boot fine. 5.10.53 to > 5.10.56 all fail as described above. > > grep ^CONFIG .config below, everything omitted is of course disabled, > including I might add CONFIG_USERFAULTFD. > > /Mikael >