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 CDE9EC74A4B for ; Mon, 13 Mar 2023 18:21:25 +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-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=rN5PxaFsDcZwzDnDfq1vaOVpcGt2OfJ2766ODSx3AKE=; b=JRQxsWUplo4mCc BouW1hKpEzjzSpk060lrO3OdDZEHcyKJCWuoJ84xO8IVcJf6s/jOPR5zuuSszVJIFZy3GoUWBBbk+ 17/1PFP52UsZeWxErWnJ0BtX5eZcXpr6ndWBwvZqNtVlfsL/ACThNHd5ep0XoBbgY8MkcE/prkgnY cmlAP8UoferD5KcwyfIZq18JC4Pvgv8NwLws/gkHdwGInS+4mxx57vSvin5NFhdZDibsI8JC/MKws ZKWSDkW5PJidi4/LT6TNbaQ4UXwfffDKjMKGrAbkOYSyu2CYU1Ev2oPiweYHw0sww2bh3xIv3Sy90 cGObRivx+vYpXrFH97sg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pbmmY-007HCu-LT; Mon, 13 Mar 2023 18:20:26 +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 1pbmmV-007HC9-LM for linux-arm-kernel@lists.infradead.org; Mon, 13 Mar 2023 18:20:25 +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 E56444B3; Mon, 13 Mar 2023 11:21:04 -0700 (PDT) Received: from e120937-lin (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 080EF3F67D; Mon, 13 Mar 2023 11:20:19 -0700 (PDT) Date: Mon, 13 Mar 2023 18:20:13 +0000 From: Cristian Marussi To: Marc Zyngier Cc: Oliver Upton , Jeremy Linton , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org, David Woodhouse , Marc Zyngier Subject: Re: Circular lockdep in kvm_reset_vcpu() ? Message-ID: References: <3496a6a10b2d8693825e733b871938f5@misterjones.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <3496a6a10b2d8693825e733b871938f5@misterjones.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230313_112023_765473_F779A33D X-CRM114-Status: GOOD ( 25.41 ) 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-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 Mon, Mar 13, 2023 at 02:09:55PM +0000, Marc Zyngier wrote: > On 2023-03-13 10:09, Cristian Marussi wrote: > > On Sat, Feb 11, 2023 at 12:56:41AM +0000, Oliver Upton wrote: > > > Hi Jeremy, > > > > > > > Hi, > > > > > On Fri, Feb 10, 2023 at 11:46:36AM -0600, Jeremy Linton wrote: > > > > Hi, > > > > > > > > I saw this pop yesterday: > > > > > > You and me both actually! Shame on me, I spoke off-list about this > > > with > > > Marc in passing. Thanks for sending along the report. > > > > > > > [ 78.333360] ====================================================== > > > > [ 78.339541] WARNING: possible circular locking dependency detected > > > > [ 78.345721] 6.2.0-rc7+ #19 Not tainted > > > > [ 78.349470] ------------------------------------------------------ > > > > [ 78.355647] qemu-system-aar/859 is trying to acquire lock: > > > > [ 78.361130] ffff5aa69269eba0 (&host_kvm->lock){+.+.}-{3:3}, at: > > > > kvm_reset_vcpu+0x34/0x274 > > > > [ 78.369344] > > > > [ 78.369344] but task is already holding lock: > > > > [ 78.375182] ffff5aa68768c0b8 (&vcpu->mutex){+.+.}-{3:3}, at: > > > > kvm_vcpu_ioctl+0x8c/0xba0 > > > > > > [...] > > > > > > > It appears to be triggered by the new commit 42a90008f890a ('KVM: Ensure > > > > lockdep knows about kvm->lock vs. vcpu->mutex ordering rule') which is > > > > detecting the vcpu lock grabbed by kvm_vcpu_ioctl() and then the kvm mutext > > > > grabbed by kvm_reset_vcpu(). > > > > > > Right, this commit gave lockdep what it needed to smack us on the head > > > for getting the locking wrong in the arm64 side. > > > > > > As gross as it might be, the right direction is likely to have our own > > > lock in kvm_arch that we can acquire while holding the vcpu mutex. > > > I'll > > > throw a patch at the list once I get done testing it. > > > > > > > I just hit this using a v6.3-rc2 and a mainline kvmtool. > > > > In my case, though, the guest does not even boot if I use more than 1 > > vcpu, which > > I suppose triggers effectively the reported possible deadlock, i.e.: > > > > root/lkvm_master run -c 4 -m 4096 -k /root/Image_guest -d > > /root/disk_debian_buster_guest.img -p "loglevel=8" > > # lkvm run -k /root/Image_guest -m 4096 -c 4 --name guest-288 > > .... > > Pass earlycon to the guest for a start. > > I seriously doubt someone has actually seen a deadlock, because > the issue has been there for at least the past 7 years... > > And -rc2 works just fine here. Thanks, I'll dig deeper what's going on un my setup. Cristian _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel