Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp230423pxj; Tue, 18 May 2021 01:57:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzQSQlnslp175gmhzROH726XMNtZsF3pE1kxafwnhygQdna8tAfM++/Npm50G3H0v5EYWbS X-Received: by 2002:a02:91c1:: with SMTP id s1mr4377578jag.61.1621328234165; Tue, 18 May 2021 01:57:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621328234; cv=none; d=google.com; s=arc-20160816; b=EtBf4HJj8/ydo+RFGj+jaPOPkUvtTbLKZtn4Oz+P4DDYmoOtVdRwWxIwURNPyv0KPV pe6D87miLtcRBpHoNQI4e91ZZHdUDpk3HJseK6vhPsTwwpz5gQWabFP0tNGMVhvSb8z2 GHBFKDxiiXTwxvQaEvha0nqZxgBRlhCBQlwuRwsmHohV6JVc/GKCKLwDesoukoQF3HfW 8zCcDDyFzGw0/0dFMScpqclbMFslS44rJyauD+imUApununoPYd4waFHOKN//S99C6Y9 WWYaqzGP6Ylu0cEQfj+jisVIBlLXD6TON46VeQ5o/xaqqoqlB1WK5Z5muOdpW3gq7ZYj CpYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=7OhFIlRMCwESMPdVJ6PCfRMCgZNdvVaOMQbK4Dv/M0I=; b=WgZBMYijghX3KmR3j/9GI60hj0hqNe/vfJtgDQX+hqM0uwNoLy+zGJIzagQjEol2I+ hmiRWc1ngBQz8Oj2CoCoH4zTSORoKnf1E3jNfN2mNcc8wg643d86Mh2NqMSrRmkgyIN+ 0/Lu/w+Y1xbw61+Z1TsSophApSDAaJkJRfv/xsrJbYeFK7Ce9S17JXfap4oBebFvRLuZ TgVtcP12h2hK4vltbA3Yru73qsUVzqgb7k4kx+nN/Xh19JKucTbceCggCvGAli1ZrxN8 INhPaOW3Ep2+AVmFfMDE79im9kG4sAN6VVHgj4VyjoalU7z+q8Pb+0+l6b/P2dhy3QHU Auiw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=WlUPF9Ip; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u11si22470412ill.6.2021.05.18.01.57.02; Tue, 18 May 2021 01:57:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=WlUPF9Ip; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240488AbhEQPDH (ORCPT + 99 others); Mon, 17 May 2021 11:03:07 -0400 Received: from mail.kernel.org ([198.145.29.99]:49498 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241201AbhEQOxB (ORCPT ); Mon, 17 May 2021 10:53:01 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 66249619B3; Mon, 17 May 2021 14:24:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1621261445; bh=8PcReOsoN6D3lryE6m6PM5J4Paqav1D+Nv8XqBH0iYw=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=WlUPF9IpYqjhO8pZXKsyU4sBshqAGtYUEfMpDuG0fCvqY0lLnJLcMa5CFi2gjW+za ZiWDizjxLrCEVc1VyCpBE/QlSWZIwlLPp4WYj6TergLhLq7FtfV7JZvxa99Ouzt5C6 RfwNNIQRJOB9O3RGLc6lWhPxI16HM9JXFjCNKyrA= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Alexey Kardashevskiy , Michael Ellerman , Sasha Levin Subject: [PATCH 5.4 046/141] powerpc/iommu: Annotate nested lock for lockdep Date: Mon, 17 May 2021 16:01:38 +0200 Message-Id: <20210517140244.325475603@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210517140242.729269392@linuxfoundation.org> References: <20210517140242.729269392@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Alexey Kardashevskiy [ Upstream commit cc7130bf119add37f36238343a593b71ef6ecc1e ] The IOMMU table is divided into pools for concurrent mappings and each pool has a separate spinlock. When taking the ownership of an IOMMU group to pass through a device to a VM, we lock these spinlocks which triggers a false negative warning in lockdep (below). This fixes it by annotating the large pool's spinlock as a nest lock which makes lockdep not complaining when locking nested locks if the nest lock is locked already. === WARNING: possible recursive locking detected 5.11.0-le_syzkaller_a+fstn1 #100 Not tainted -------------------------------------------- qemu-system-ppc/4129 is trying to acquire lock: c0000000119bddb0 (&(p->lock)/1){....}-{2:2}, at: iommu_take_ownership+0xac/0x1e0 but task is already holding lock: c0000000119bdd30 (&(p->lock)/1){....}-{2:2}, at: iommu_take_ownership+0xac/0x1e0 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&(p->lock)/1); lock(&(p->lock)/1); === Signed-off-by: Alexey Kardashevskiy Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20210301063653.51003-1-aik@ozlabs.ru Signed-off-by: Sasha Levin --- arch/powerpc/kernel/iommu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/powerpc/kernel/iommu.c b/arch/powerpc/kernel/iommu.c index 9704f3f76e63..d7d42bd448c4 100644 --- a/arch/powerpc/kernel/iommu.c +++ b/arch/powerpc/kernel/iommu.c @@ -1057,7 +1057,7 @@ int iommu_take_ownership(struct iommu_table *tbl) spin_lock_irqsave(&tbl->large_pool.lock, flags); for (i = 0; i < tbl->nr_pools; i++) - spin_lock(&tbl->pools[i].lock); + spin_lock_nest_lock(&tbl->pools[i].lock, &tbl->large_pool.lock); iommu_table_release_pages(tbl); @@ -1085,7 +1085,7 @@ void iommu_release_ownership(struct iommu_table *tbl) spin_lock_irqsave(&tbl->large_pool.lock, flags); for (i = 0; i < tbl->nr_pools; i++) - spin_lock(&tbl->pools[i].lock); + spin_lock_nest_lock(&tbl->pools[i].lock, &tbl->large_pool.lock); memset(tbl->it_map, 0, sz); -- 2.30.2