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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 71666C433F5 for ; Wed, 15 Dec 2021 12:30:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:From:References:Cc:To:Subject: MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=NPfQNRt+/mwDn3XTSvZDBw5AxlLLBJ11rb/LwdmX20Y=; b=ZBx8xdi1n54Hbf KI8bPmLcMdwXNGdR5RJRA9+STI9Etuen/ITsibkipbgY7CIssb5iW+DB8puPK1XRv6NCbYhmP5urW IsMQa9IlqWLOBFhAdpUhk3b1OLJ4/3q5EgnJPAzBHatTQvd9iHAh30cFU2zuu1fHeLhjpfG1TT9Po uWQWbWIvLbH+rOqQzWu/rtadVAROgjB/HlzHGCPhhuF4h28TeJEKcz+fuywLE49F3ubYFC3stsrJC p/qsLmooZ018P5XhO7+yIaJok1ZG328X2vKNNL3iCJjtF0waOiI1ptbyC71CcBU1uS8iY9V7tMZLj PpWuLwYB7srZRFiasBmw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mxTPe-000nTm-SK; Wed, 15 Dec 2021 12:29:38 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mxTPa-000nSh-KA for linux-arm-kernel@lists.infradead.org; Wed, 15 Dec 2021 12:29:36 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 9700CD6E; Wed, 15 Dec 2021 04:29:31 -0800 (PST) Received: from [10.57.34.58] (unknown [10.57.34.58]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 093E43F774; Wed, 15 Dec 2021 04:29:29 -0800 (PST) Message-ID: <96bbd76e-3667-749a-1fda-458e6fa40a27@arm.com> Date: Wed, 15 Dec 2021 12:29:25 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: ARM64 kernel crash Content-Language: en-GB To: Mark Rutland , tjcw@cantab.net Cc: linux-kernel@vger.kernel.org, Chris Ward , linux-arm-kernel@lists.infradead.org References: From: Robin Murphy In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211215_042934_745348_E5D9F545 X-CRM114-Status: GOOD ( 19.77 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 2021-12-15 10:53, Mark Rutland wrote: > Hi Chris, > > On Wed, Dec 15, 2021 at 07:36:34AM +0000, Chris Ward wrote: >> Please personally cc me on answers/comments as I am not currently >> subscribed to the LKML. >> Trying again because I messed up the format badly the first time >> round. Apologies for that. > > For arm/arm64 stuff, it's best to also Cc LAKML > (linux-arm-kernel@lists.infradead.org). I've added that here, and for the > benefit of others I've kept your entire mail as context. In future replies I > will trim this. > > Please also note that kernel mailing list style is to reply inline (as I've don > with this mail) rather than to top-post. That helps to keep discussions > legible, and makes it possible to trim irrelevant context. Please keep any > replies in kind with that style. > >> My team has a problem which is being bounced between Canonical support >> and Xilinx support. >> We are using kernel 5.4.0-xilinx-v2020.2 built from sources under >> https://github.com/Xilinx/linux-xlnx with a Ubuntu 20.04 userland on >> an ARM64 embedded linux machine (i.e. not x86-64). > > Can you share the config used? e.g. was that `defconfig`, or something else? > >> When trying to set up a file system on a ramdisk, we get a kernel crash for >> sizes of ramdisk larger than 2GB while trying to 'dd if=/dev/zero ...' in >> preparation for issuing mkfs. FWIW "larger than 2GB" immediately stands out as a massive red flag for signed integer overflow leading to memory corruption *somewhere*, and all the splats in the log below do look like they could simply be fallout from that. Building the vendor kernel with KASAN enabled might be another worthwhile avenue of investigation - if that can flag up a wild memory access at the point where it actually occurs, you've got more chance of working backwards from there to the root cause. Robin. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel