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 028C0C433EF for ; Thu, 10 Mar 2022 22:09:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344221AbiCJWKn (ORCPT ); Thu, 10 Mar 2022 17:10:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33646 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343815AbiCJWKk (ORCPT ); Thu, 10 Mar 2022 17:10:40 -0500 Received: from pandora.armlinux.org.uk (pandora.armlinux.org.uk [IPv6:2001:4d48:ad52:32c8:5054:ff:fe00:142]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 29504DA87C; Thu, 10 Mar 2022 14:09:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=n6DIoThXu6+2o1MnVoANgPmGbVAPFUq9XQ9ZlvmYihM=; b=svgcWFlC7tHQ4R+LvnKXqtgZtW odGemenDWx2KeCUZx3WC3v3olcCJV73vy7HM9BT2Ec0cDz/8BADaQUSn+mjZIMH9WM/v8O38MMwd1 GvI4e+XOlhkjsqRR8qOyv/gElZDz13MW6yFbplaGOvNKMvWct2ni2gIbMmrU0f5JC6/HI75LsczPm o7mvs+3WWcbtUczqBxxVOljqZi+srtZ2mIMqLdiU+IXmmymMQzn5kP9suKZyvS1LHdhOzXiOjhtS0 Fvt92G12OPL6it1IdiQbEdsqu8hVmvhbfXU/mumi7n3Ndjjd2zugyrSTlekVmX6alP6vA4edIreyr Og6UkRJw==; Received: from shell.armlinux.org.uk ([fd8f:7570:feb6:1:5054:ff:fe00:4ec]:57780) by pandora.armlinux.org.uk with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nSQyQ-0001jL-N3; Thu, 10 Mar 2022 22:09:31 +0000 Received: from linux by shell.armlinux.org.uk with local (Exim 4.94.2) (envelope-from ) id 1nSQyO-0000xj-3P; Thu, 10 Mar 2022 22:09:28 +0000 Date: Thu, 10 Mar 2022 22:09:28 +0000 From: "Russell King (Oracle)" To: Ard Biesheuvel Cc: Naresh Kamboju , open list , Linux-Next Mailing List , Linux ARM , Linus Walleij , Arnd Bergmann , Corentin Labbe , Stephen Rothwell Subject: Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: Russell King (Oracle) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 10, 2022 at 11:06:17PM +0100, Ard Biesheuvel wrote: > On Thu, 10 Mar 2022 at 22:50, Naresh Kamboju wrote: > > > > On Fri, 11 Mar 2022 at 02:55, Ard Biesheuvel wrote: > > > > > > On Thu, 10 Mar 2022 at 22:18, Naresh Kamboju wrote: > > > > > > > > Hi Ard and Russell, > > > > > > > > The boot test pass on linux next-20220310 tag with KASAN=y on BeagleBoard x15 > > > > device. but LTP cve tests reproduced the reported kernel crash [1]. > > > > From the available historical data I can confirm that this is an > > > > intermittent issue on > > > > BeagleBoard x15 devices. > > > > > > > > OTOH, the kernel crash is always reproducible on qemu-arm with KASAN=y > > > > while booting which has been known to fail for a long time. > > > > > > > > From the Ardb tree I have boot tested qemu-arm with KASAN=y the reported > > > > kernel crash is always reproducible. > > > > > > > > The build steps [3] and extra Kconfigs. > > > > > > > > - Naresh > > > > [1] https://lkft.validation.linaro.org/scheduler/job/4701310 > > > > [2] https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/ > > > > [3] https://builds.tuxbuild.com/2661dIAPUjE2DMJvye91He2gus0/tuxmake_reproducer.sh > > > > > > Thanks Naresh. I'm having trouble to make sense of this, though. The > > > linked output log appears to be from a build that lacks my 'ARM: > > > entry: fix unwinder problems caused by IRQ stacks' patch, as it > > > doesn't show any occurrences of call_with_stack() on any of the call > > > stacks. > > > > > > Do you have a link to the vmlinux and zImage files for this build? > > > > Yes. > > > > vmlinux.xz: https://builds.tuxbuild.com/26BmIasJnAyCii0SkgbKarkF369/vmlinux.xz > > zImage: https://builds.tuxbuild.com/26BmIasJnAyCii0SkgbKarkF369/zImage > > System.map: https://builds.tuxbuild.com/26BmIasJnAyCii0SkgbKarkF369/System.map > > Build log: https://builds.tuxbuild.com/26BmIasJnAyCii0SkgbKarkF369/ > > > > This kernel does not appear to have > > ARM: unwind: set frame.pc correctly for current-thread unwinding > ARM: entry: fix unwinder problems caused by IRQ stacks > ARM: Revert "unwind: dump exception stack from calling frame" > > so it is expected that the same issue is still being observed. > > Could you please try -next with those patches applied? I concur, from my inspection of the above referenced vmlinux file. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!