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 A5107C64EC4 for ; Mon, 13 Feb 2023 09:32:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230266AbjBMJcG (ORCPT ); Mon, 13 Feb 2023 04:32:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37500 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229799AbjBMJbh (ORCPT ); Mon, 13 Feb 2023 04:31:37 -0500 Received: from desiato.infradead.org (desiato.infradead.org [IPv6:2001:8b0:10b:1:d65d:64ff:fe57:4e05]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6E68816AD2; Mon, 13 Feb 2023 01:30:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=desiato.20200630; 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=tlbtwloiMll80xsCP5JxReJzFyl0pMq9yses5MAk/Hw=; b=EYMskAFjqDUuDsKVLxh5WJIqSN 9XYUb/9Hr+XOo0u6+DfjwQDUegFHC1KiigfqbFKStMj5kZI8KZ1SoWFyvK0yfn/8Xa5/wGs30bpbT Drh84WYjg2KkeqDXPOB9B6trmp6a9R4ODGiG9eNDZ5YauLGcoS/TjTzTuZMzQH5pw7VKlRMlI+D6V VMGzZ2lHYiV6Oe3JzW8HSv7afWIG2EcS3S/MNLTg4jHV28cOk1JcamPznuzmmm5ua9WETKww8yhz0 rwcRU6ureLuNr7XmlGivnHo/9Ue4C7e0lf02weexO7gCw8+Y359T40Nv4v3SVdj+1BMLQ4dB57xK+ XwyHc/qQ==; Received: from j130084.upc-j.chello.nl ([24.132.130.84] helo=noisy.programming.kicks-ass.net) by desiato.infradead.org with esmtpsa (Exim 4.96 #2 (Red Hat Linux)) id 1pRV6d-009Fkm-2F; Mon, 13 Feb 2023 09:28:40 +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 2014F30036B; Mon, 13 Feb 2023 10:27:19 +0100 (CET) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 0531520C6EEA1; Mon, 13 Feb 2023 10:27:18 +0100 (CET) Date: Mon, 13 Feb 2023 10:27:18 +0100 From: Peter Zijlstra To: Alan Stern Cc: Kent Overstreet , 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:19:16PM -0500, Alan Stern wrote: > (Device names are often set after the device is initialized. Does > lockdep mind if a lock_class_key's name is changed after it has been > registered?) It does, althought I don't at the moment recall how hard it would be to change that.