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 D2E9EC001B0 for ; Mon, 3 Jul 2023 10:05:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229942AbjGCKFQ (ORCPT ); Mon, 3 Jul 2023 06:05:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33292 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231268AbjGCKEz (ORCPT ); Mon, 3 Jul 2023 06:04:55 -0400 Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D37B8E74 for ; Mon, 3 Jul 2023 03:04:06 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 008413200909; Mon, 3 Jul 2023 06:04:01 -0400 (EDT) Received: from imap51 ([10.202.2.101]) by compute6.internal (MEProxy); Mon, 03 Jul 2023 06:04:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arndb.de; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1688378641; x=1688465041; bh=XD MTdubj4bFh9b2AITgPBVqq5Be93OkL1yTP/pmBOI8=; b=gb2LnScsr4wdBbRVZd Vrn4qPQGFGMPWyKRGLG4OBK8+basSfJduDyWmZvhDc1vg0xk7LDG6/a7fWVxZLlM +tkl7cQ4LKmKSAuGNRHyhL/2ew4kHyMk0WJ/dsEe2g0TVkbUBUtni9OJ9vmUVVG5 z4V4p6f5j2HFVetEskzkcfHb+RGmgm2FfVSSv6W0NuSuFsBUn/ctzvbYPYAWuC2e 59HWu7ruHlqgPI5imbTIxVVXQuNTkefIdFTww+4rXFV4Qblz3z+1rCL7WyMlMdIR Z34bBcq8ybXctQdgALhWsBb/kk9fLmd9b4fNlJwl3zlTDxXCumDR806WbR5Ul9l2 ZcMg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1688378641; x=1688465041; bh=XDMTdubj4bFh9 b2AITgPBVqq5Be93OkL1yTP/pmBOI8=; b=NKEZ8MHL9NSJNbGwY6IsT+NL5twVY IDVrUISXktuA5JqoKrpZr0pJgHJOluJt3209N7TeBTao+WlsOiKz+CaLXK8Pjrqd nZ6UBvoJEbxWNKThdj4yEWJKecb5P+pqhZZVRJrCELgsqBvoRDbb2uncqc51Odj4 wQQTg5H4lPGL7M1FiveMVTu0CynVZFFiDHoWC2IkR8G6ZsJZv+RZjnjzZP2YLkNg WnNsNohjZ+u7MJlw76n7LsoedzhR/oYE1pOWpBeo+oig8/sZ1RwPCn2ctdJ6lCDb fiG2FpOILvXpYWRbc6hq+V+atlPrMqoD9LuLyfrE5Bl0BPLff4D3zIKlg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedruddvgddvvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvvefutgesthdtredtreertdenucfhrhhomhepfdetrhhn ugcuuegvrhhgmhgrnhhnfdcuoegrrhhnugesrghrnhgusgdruggvqeenucggtffrrghtth gvrhhnpeffjeduteevtedvtddvgfffleefvdekhfefgeelvedtkeffffegveehheefvdfh ieenucffohhmrghinhepthhugihsuhhithgvrdgtohhmpdhkvghrnhgvlhdrohhrghenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrrhhnuges rghrnhgusgdruggv X-ME-Proxy: Feedback-ID: i56a14606:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 380D5B60086; Mon, 3 Jul 2023 06:04:01 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-527-gee7b8d90aa-fm-20230629.001-gee7b8d90 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Mon, 03 Jul 2023 12:03:38 +0200 From: "Arnd Bergmann" To: "Mark Rutland" , "Naresh Kamboju" Cc: "open list" , lkft-triage@lists.linaro.org, "Frederic Weisbecker" , "Paul E. McKenney" , "Anders Roxell" , "Dan Carpenter" , "Kees Cook" Subject: Re: qemu-arm64: Unexpected kernel BRK exception at EL1 - WARNING: CPU: 3 PID: 0 at kernel/context_tracking.c:128 ct_kernel_exit.constprop Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 3, 2023, at 11:51, Mark Rutland wrote: > On Mon, Jul 03, 2023 at 12:02:22PM +0530, Naresh Kamboju wrote: >> On Sun, 2 Jul 2023 at 13:56, Arnd Bergmann wrote: >> > On Sat, Jul 1, 2023, at 10:42, Naresh Kamboju wrote: >> > >> >> Here is the build artifacts location with kselftest merge configs. >> https://storage.tuxsuite.com/public/linaro/lkft/builds/2Rum1V78RQJMftEanwtN28dApDO/ > > In your .config here, I note you have: > > | CONFIG_UBSAN_TRAP=y > > Can you try this with CONFIG_UBSAN_TRAP=n ? > >> [ 56.150153] Modules linked in: crct10dif_ce sm3_ce sm3 sha3_ce >> sha512_ce sha512_arm64 cfg80211 bluetooth rfkill sch_fq_codel fuse drm >> [ 56.151781] CPU: 0 PID: 438 Comm: seccomp_bpf Not tainted 6.4.0 #1 >> [ 56.152043] Hardware name: linux,dummy-virt (DT) >> [ 56.152396] pstate: 41400005 (nZcv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) >> [ 56.152667] pc : alloc_pid+0x3b4/0x3c8 >> [ 56.154243] lr : alloc_pid+0x140/0x3c8 > > Looking at objdump, that's: > > | ffff8000800d73b0 : > | ... > | ffff8000800d7764: d4207d00 brk #0x3e8 > > ... and addr2line fingers this as: > > | [mark@lakrids:~/tmp-naresh-kamboju]% usekorg 10.3.0 > aarch64-linux-addr2line -ife vmlinux ffff8000800d7764 > > | alloc_pid > | /builds/linux/kernel/pid.c:244 > > ... which appears to be: > > | 244 pid->numbers[i].nr = nr; > > Full objdump of the function below; as above I suspect this is UBSAN triggering > a __builtin_trap() on an out-of-range access. It looks like a fix has already made it into mainline now, so it should be fixed on the latest linux-next: https://lore.kernel.org/lkml/20230630180418.gonna.286-kees@kernel.org/ arnd