Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp176695pxj; Tue, 18 May 2021 00:22:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzr6Wr5YFCUYBQj40BiF0eLOcc2ofo+cIuAcW5KL8mUz2g7vEuG6JW1fKyfSTZ4WRU3Sp2w X-Received: by 2002:a50:eb08:: with SMTP id y8mr5353951edp.89.1621322538374; Tue, 18 May 2021 00:22:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621322538; cv=none; d=google.com; s=arc-20160816; b=fzk53BIHoce9q6MnnLi29JWkkZ0kG8Oef/brXvX7RiNsqByllYs+Y1WC2Cv2YkrSVA w1Rnx2MkWDodk4bMOMnZXXPpoI0nZy3YTXbkJCl+wKJ9fsGIf/ZpRuz/gOElH0O+BFpv 9mdHvnirpGEjqzvwjE7pJcey4yahOfsfRWKGDBtESpGO/O2tAzXHRuLOB6qme55FUpAl DJj8W9uxwVe1VXf3v27ew0zZJE1x/XWrMZfk8neTgj4fehwtXAxCcfWe5J4i3FZ4y8Xy /VFcWmgFIJyn0MySqnhvog4c9PT1jbndatbWXEDN533/SKLxkcYpBLtC2MUB5ha6KRhG IJuw== 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=y+OeFvHEgoSQFwqdQn+JJKX/X5n6EQwdaTKJ2E1GS2Q=; b=UVJ3jY4X3XkuMbkq4arreSbAxZ85ePw5fUNFZ/wOH68NfzosU3La/YAl9BoZrl7Cie Uxn7umk7U6n2kTPkX2NzaCCvX/gNIHD10sao9Se/1vQFwTJcu196ep7qQKqdzR+UUoLT I+a6tupXa1xtNXw44Xfrkmeqqf+vUzSx745A48s6pMTqDdXN0sOjcNRc3qIcr4N409vH dxUVy4ta7FmcfN+23RGjWVyrAibWadpJhjyw7LllGVgkjPiAinGvLgJ4KAsZUrpg9JMn WbwoT0u28If4K4AIFmSV/OixmZFpmsBIgCqhb4fLa5KBBpygtTb4zasfMvbKEwwyiB5h phWg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=wTeN67gr; 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 n21si16571968ejg.609.2021.05.18.00.21.55; Tue, 18 May 2021 00:22:18 -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=wTeN67gr; 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 S242333AbhEQOzG (ORCPT + 99 others); Mon, 17 May 2021 10:55:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:39742 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240894AbhEQOql (ORCPT ); Mon, 17 May 2021 10:46:41 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 7598E61423; Mon, 17 May 2021 14:21:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1621261309; bh=w1k4f0i6yOmkScwiFjhzfL8jY/5nHyF4SbdTGYR6oc4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=wTeN67grELFXoOe0rfBWqyKDpNZW2Rkkv9Sb/LDQ1lOY/ojI7jwTD3mf04JEfQRZ3 hkit7/MZvvcbckgORdYjCY8ZipEOVRDD2sTtPgy3AbJJLnOPV3808VP7vnH4cv1iwa kfxc4j+PWQqSFkhpNh+CMUZemI/Xpcdda67Y3fsc= 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.11 100/329] powerpc/iommu: Annotate nested lock for lockdep Date: Mon, 17 May 2021 16:00:11 +0200 Message-Id: <20210517140305.506467681@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210517140302.043055203@linuxfoundation.org> References: <20210517140302.043055203@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 5b69a6a72a0e..6806eefa52ce 100644 --- a/arch/powerpc/kernel/iommu.c +++ b/arch/powerpc/kernel/iommu.c @@ -1050,7 +1050,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); @@ -1078,7 +1078,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