Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp3660045iog; Mon, 27 Jun 2022 23:15:19 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vttSar+T9yOwjYf08vqKbOGtAGV3SFfK0amGu9JWi9+ansQdum6pBTzkqsVj7hxw0Z4azA X-Received: by 2002:a17:90b:33cc:b0:1ec:b279:69fa with SMTP id lk12-20020a17090b33cc00b001ecb27969famr26148278pjb.70.1656396919341; Mon, 27 Jun 2022 23:15:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656396919; cv=none; d=google.com; s=arc-20160816; b=mq2hW6ahwm3o/gn2YC/TvafBKMFRGkLei1GuAW5zDL0RVcw4+vJgFQhFJZnoDesxA7 JJYZFEDoqXyUdOqOl5qNmr2Kk0Go1+W/4i8Utj/9BcrvkLGLJKnpRQOnzyAo2iGobIhG T1WY51J9seWS6BnHvouPe1RjeIsrizo9ygSmBortCEzgnPoDJLvEhxfcjtRViGZko4v3 /JIsPJeCz5c9UJbgn8PwXCQiwmBbsVl39UiPrNuC6PQj3Xc9gAF6r2HXUGGNMhlzXzeW NpNAK4VY/EsQr7ntzQqOUXYLcLUFb9md5Kr64T6SO82AkJWTPr8n6Z6QEwuawqFBlr78 JrUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=cWTx7PINDz3qrfvrgx0IhWSEM1DCqLWtUdDXr1e69z4=; b=BE+LuPzd1xRUvsZu6JkolodAI6GWdsxicV1tY3SwytguV3uDHfujgCRStXN6h2223C BVw1RY4s2Rs0BIDxIpmTt/y9VBS2BGW6oUQJSE5d9JU0TFTmQ1Dh7d9F5/Caymw+C0Cp 9Xtj08IqLD62KfIm7kqbQd5VnZdGB+uJMYGWv8xNN3xX2a7WbL18906NNEqbptkvciHw iyoJeu/bzAp30DlkkOXUu3qVCVAtaH5GWP4TwE9b3i3/dJa63r7QIsBzFQbtsce3nk2G XDSkKIDxgvBCDMf5PlPVy2hwFakcKgpyBY9OK/Dl8eQCFUgSnRZVDnP+uJ683YQJUWFy evmw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=bombadil.20210309 header.b=TjZz3Ktj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id n1-20020a170902f60100b0016198140119si16915395plg.606.2022.06.27.23.15.07; Mon, 27 Jun 2022 23:15:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@infradead.org header.s=bombadil.20210309 header.b=TjZz3Ktj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245390AbiF1GKL (ORCPT + 99 others); Tue, 28 Jun 2022 02:10:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46938 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245380AbiF1GKK (ORCPT ); Tue, 28 Jun 2022 02:10:10 -0400 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4BF2D60DB; Mon, 27 Jun 2022 23:10:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=cWTx7PINDz3qrfvrgx0IhWSEM1DCqLWtUdDXr1e69z4=; b=TjZz3KtjB/7fWIyslR8RRUlKxf xQfFOTQgIo7a7z79wl4inK+vmvst9+VyRoNVkUKUbcD+ZEhs2RP780eErLQLVsgG5DUZxmM0frTNU oRMmZm+R3y1wIBs+6yyLAzLhADOFBZE+OcQ2eu4nsjTsaIx9BIOExIgrRVK3a6h63IidUsSS/PbdX wtQgqfqJOFpol4/dj2DVDopVgaOWrRWMJLagCZnTIMweW8e8I7nGgQcb4P9l0WC/YBiacImz2GXCI 0RDeh1AZuMmh4xByl6K+V6EQMHZkp6q/Sz2iuAwSFGmkw6L2pz6OED/KIh73gYMvpdtLxAXws1sCJ Cetoedrg==; Received: from hch by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1o64Q9-004b4e-NJ; Tue, 28 Jun 2022 06:09:57 +0000 Date: Mon, 27 Jun 2022 23:09:57 -0700 From: Christoph Hellwig To: Greg Kroah-Hartman Cc: "yangx.jy@fujitsu.com" , Tejun Heo , Bjorn Helgaas , Jason Gunthorpe , Leon Romanovsky , "linux-kernel@vger.kernel.org" , "linux-rdma@vger.kernel.org" , "linux-block@vger.kernel.org" Subject: Re: [bug report from blktests nvme/032] WARNING: possible circular locking dependency detected Message-ID: References: <4ed3028b-2d2f-8755-fec2-0b9cb5ad42d2@fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 28, 2022 at 08:07:52AM +0200, Greg Kroah-Hartman wrote: > On Tue, Jun 28, 2022 at 04:03:55AM +0000, yangx.jy@fujitsu.com wrote: > > Hi everyone, > > > > Running blktests nvme/032 on kernel v5.19-rc2+ which enables > > CONFIG_LOCKDEP and CONFIG_PROVE_LOCKING triggered the below WARNING. > > What was happening when this trace was created? It looks like you were > manually removing a PCI device from the system through sysfs? Why would > blktests do that? To test how the block layer copes with the fact that the underlying device goes away.