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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E3D13C636D7 for ; Mon, 13 Feb 2023 09:32:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230423AbjBMJcV (ORCPT ); Mon, 13 Feb 2023 04:32:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36060 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230361AbjBMJbu (ORCPT ); Mon, 13 Feb 2023 04:31:50 -0500 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E3A3C199DD; Mon, 13 Feb 2023 01:30:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; 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=SUtoERbxWFSwupPXeH5TrcEuh4VbNJCgfwYwJDpRLqM=; b=eD6reRK7jGipCYX9Uigst9vFk3 1RRafOh0/Zmvg7sJBHNNiUBhoSN/sIzJ0NGzeVdnZnWwNtdwLEBxCL+cdoIOS7rBfExs1d220mRpY Js1njJKUVaWNy7SWVV1ZwBBhiPnGXIdijRRbC7H0f2OEDnBit8mAOpSKa5c1WHSZRft2jF49288VQ NQxl9tra5h2OVaam9e91fjoaEd7rbXx76Jp3eVq9L7+6lIPNZcUoF/aFfnaeW3n6tQblj3VWouvPX FwyXmEcr4LnNWBdN5BbYiwnQMmeKzm1g3kfUFCJBE4tW5rX1THasY6UISkvnGnOx1yhddrGliACaz gYgg8FqQ==; Received: from j130084.upc-j.chello.nl ([24.132.130.84] helo=noisy.programming.kicks-ass.net) by casper.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1pRV9i-005c7m-51; Mon, 13 Feb 2023 09:29:50 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id B29F230049E; Mon, 13 Feb 2023 10:29:49 +0100 (CET) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 9AF6E20C6EEA1; Mon, 13 Feb 2023 10:29:49 +0100 (CET) Date: Mon, 13 Feb 2023 10:29:49 +0100 From: Peter Zijlstra To: Kent Overstreet Cc: Alan Stern , Kent Overstreet , Linus Torvalds , Coly Li , Tetsuo Handa , syzkaller , Dmitry Vyukov , Greg Kroah-Hartman , "Rafael J. Wysocki" , Ingo Molnar , Boqun Feng , LKML , USB list , Hillf Danton Subject: Re: [PATCH RFC] drivers/core: Replace lockdep_set_novalidate_class() with unique class keys Message-ID: References: <109c3cc0-2c13-7452-4548-d0155c1aba10@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Feb 12, 2023 at 03:51:05PM -0500, Kent Overstreet wrote: > But, this would add a lot of complexity to lockdep, and this is the sort > of situation where if you have a bug in the comparison function (i.e. it > doesn't define a total ordering) it'll break things in terribly fun > ways. FWIW, it is possible to annotate an actual deadlock away with many of the lockdep annotations -- care is always needed with this stuff.