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=-5.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 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 B9289C2D0E4 for ; Fri, 20 Nov 2020 18:58:31 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 44D31207D3 for ; Fri, 20 Nov 2020 18:58:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="wnMr7zQ6"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="wJPsspjB" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 44D31207D3 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:Reply-To:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=uHqpMIT/zG7cItJ98PhMhtsD1fAni/Bsnu4ETrk6duw=; b=wnMr7zQ6ZZfUR658LMZX3ka9JB ilMuDgG/e0boevGpAeDh9L56ilo9n2VlWbPEkp5GdBZ0fGBwbXDs7DA/BpSx16eej9FGm9K2vpvTY J38VRq0L5+DN2NBhblH0B4D71QXBSb51sDFC62bhWj2ZvH9SM9QLCpnh6P62/ib9R+H7+ACWNeIBv /ulZvZOIh84kaosLKStqYSz31O0jeLG/1x0yeZLuo16/1BC2YN4Hl6+FRTyfWaEF2ai7dGdZtX5WY ovSdHspzL+IAGlxlJK6gsolJhUuesBk1ybzp7sHYF57W/E2Jd/OrWBUxToBwq6h5ps9XdkmASTZnX XoiwV3CA==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kgBbf-0007q9-MZ; Fri, 20 Nov 2020 18:58:03 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kgBbb-0007oM-5Q for linux-arm-kernel@lists.infradead.org; Fri, 20 Nov 2020 18:58:01 +0000 Received: from paulmck-ThinkPad-P72.home (50-39-104-11.bvtn.or.frontiernet.net [50.39.104.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4C01222464; Fri, 20 Nov 2020 18:57:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1605898678; bh=XFTcuGAvqGRf8jCZ+ckM7jc3MC3vlz4De93JWXGu/Ro=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=wJPsspjBAtc2Maj5KcKF0b+v14djW14eYbsjEMFBRVZNoUZEi2q5wc0RTCHU1qYt0 jQ6XGn+h3U1TMAK7Hh1puIJu2qQCcqYlWwMKw10ke/QJPL7eFZMkuHm4oninm8u0Rt WxdDT/4XnMTOFNIZZF4Uy4osU6s31bBTiWBAv5K4= Received: by paulmck-ThinkPad-P72.home (Postfix, from userid 1000) id E2B203522637; Fri, 20 Nov 2020 10:57:57 -0800 (PST) Date: Fri, 20 Nov 2020 10:57:57 -0800 From: "Paul E. McKenney" To: Mark Rutland Subject: Re: linux-next: stall warnings and deadlock on Arm64 (was: [PATCH] kfence: Avoid stalling...) Message-ID: <20201120185757.GL1437@paulmck-ThinkPad-P72> References: <20201119151409.GU1437@paulmck-ThinkPad-P72> <20201119170259.GA2134472@elver.google.com> <20201119184854.GY1437@paulmck-ThinkPad-P72> <20201119193819.GA2601289@elver.google.com> <20201119213512.GB1437@paulmck-ThinkPad-P72> <20201120141928.GB3120165@elver.google.com> <20201120143928.GH1437@paulmck-ThinkPad-P72> <20201120152200.GD2328@C02TD0UTHF1T.local> <20201120173824.GJ1437@paulmck-ThinkPad-P72> <20201120180206.GF2328@C02TD0UTHF1T.local> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20201120180206.GF2328@C02TD0UTHF1T.local> User-Agent: Mutt/1.9.4 (2018-02-28) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201120_135759_521981_A8F2F049 X-CRM114-Status: GOOD ( 35.51 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: paulmck@kernel.org Cc: linux-arm-kernel@lists.infradead.org, Marco Elver , Anders Roxell , Jann Horn , Peter Zijlstra , Lai Jiangshan , Linux Kernel Mailing List , Steven Rostedt , rcu@vger.kernel.org, Linux-MM , Alexander Potapenko , kasan-dev , Tejun Heo , Andrew Morton , Dmitry Vyukov Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Nov 20, 2020 at 06:02:06PM +0000, Mark Rutland wrote: > On Fri, Nov 20, 2020 at 09:38:24AM -0800, Paul E. McKenney wrote: > > On Fri, Nov 20, 2020 at 03:22:00PM +0000, Mark Rutland wrote: > > > On Fri, Nov 20, 2020 at 06:39:28AM -0800, Paul E. McKenney wrote: > > > > On Fri, Nov 20, 2020 at 03:19:28PM +0100, Marco Elver wrote: > > > > > I found that disabling ftrace for some of kernel/rcu (see below) solved > > > > > the stalls (and any mention of deadlocks as a side-effect I assume), > > > > > resulting in successful boot. > > > > > > > > > > Does that provide any additional clues? I tried to narrow it down to 1-2 > > > > > files, but that doesn't seem to work. > > > > > > > > There were similar issues during the x86/entry work. Are the ARM guys > > > > doing arm64/entry work now? > > > > > > I'm currently looking at it. I had been trying to shift things to C for > > > a while, and right now I'm trying to fix the lockdep state tracking, > > > which is requiring untangling lockdep/rcu/tracing. > > > > > > The main issue I see remaining atm is that we don't save/restore the > > > lockdep state over exceptions taken from kernel to kernel. That could > > > result in lockdep thinking IRQs are disabled when they're actually > > > enabled (because code in the nested context might do a save/restore > > > while IRQs are disabled, then return to a context where IRQs are > > > enabled), but AFAICT shouldn't result in the inverse in most cases since > > > the non-NMI handlers all call lockdep_hardirqs_disabled(). > > > > > > I'm at a loss to explaim the rcu vs ftrace bits, so if you have any > > > pointers to the issuies ween with the x86 rework that'd be quite handy. > > > > There were several over a number of months. I especially recall issues > > with the direct-from-idle execution of smp_call_function*() handlers, > > and also with some of the special cases in the entry code, for example, > > reentering the kernel from the kernel. This latter could cause RCU to > > not be watching when it should have been or vice versa. > > Ah; those are precisely the cases I'm currently fixing, so if we're > lucky this is an indirect result of one of those rather than a novel > source of pain... Here is hoping! > > I would of course be most aware of the issues that impinged on RCU > > and that were located by rcutorture. This is actually not hard to run, > > especially if the ARM bits in the scripting have managed to avoid bitrot. > > The "modprobe rcutorture" approach has fewer dependencies. Either way: > > https://paulmck.livejournal.com/57769.html and later posts. > > That is a very good idea. I'd been relying on Syzkaller to tickle the > issue, but the torture infrastructure is a much better fit for this > problem. I hadn't realise how comprehensive the scripting was, thanks > for this! But why not both rcutorture and Syzkaller? ;-) > I'll see about giving that a go once I have the irq-from-idle cases > sorted, as those are very obviously broken if you hack > trace_hardirqs_{on,off}() to check that RCU is watching. Sounds good! Thanx, Paul _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel