From mboxrd@z Thu Jan 1 00:00:00 1970 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 EEBE0C77B75 for ; Tue, 9 May 2023 19:31:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234751AbjEITb7 (ORCPT ); Tue, 9 May 2023 15:31:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56888 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233625AbjEITb6 (ORCPT ); Tue, 9 May 2023 15:31:58 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 63BC6E71; Tue, 9 May 2023 12:31:57 -0700 (PDT) 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=AdywwhjxGaN6Y3/mPqh/c2MgjoXsXtnSQ+Kliw53l+c=; b=c2W8uSumZRfddTrbKo2ykCgH54 +188v8gGxJC+y2pNBcq5OTBhzwJbjENdEsXKTGm/pqr5iWlNxUEm/Cx/rHIeM39FkpQuCIMESBwB8 dUB3A23nwrwZpkZVIfVj54PWZbxgTteGErtwYkVVree8SgEyRtq1E0CZY6Wojoftyeh9g2d8ZcRuL 7VqPvD+ErYEBEHftquqIlQvfAEhM848aIO8fNomchCorgWHd4AC8Nvel5XYkAI4qDuI+dTng/fg0A sXM8OeB54k+DZX3hMs4uNmwnaXAnYxG31UZsyts8TFPwydNpH2NaQ5lK+m6OQ4727cUkGXcEIbrGg WgcN5lew==; 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 1pwT3r-00FY08-U2; Tue, 09 May 2023 19:31:48 +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 87142300786; Tue, 9 May 2023 21:31:47 +0200 (CEST) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 7866221F9F5C4; Tue, 9 May 2023 21:31:47 +0200 (CEST) Date: Tue, 9 May 2023 21:31:47 +0200 From: Peter Zijlstra To: Kent Overstreet Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-bcachefs@vger.kernel.org, Ingo Molnar , Will Deacon , Waiman Long , Boqun Feng Subject: Re: [PATCH 03/32] locking/lockdep: lockdep_set_no_check_recursion() Message-ID: <20230509193147.GC2148518@hirez.programming.kicks-ass.net> References: <20230509165657.1735798-1-kent.overstreet@linux.dev> <20230509165657.1735798-4-kent.overstreet@linux.dev> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230509165657.1735798-4-kent.overstreet@linux.dev> Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Tue, May 09, 2023 at 12:56:28PM -0400, Kent Overstreet wrote: > This adds a method to tell lockdep not to check lock ordering within a > lock class - but to still check lock ordering w.r.t. other lock types. > > This is for bcachefs, where for btree node locks we have our own > deadlock avoidance strategy w.r.t. other btree node locks (cycle > detection), but we still want lockdep to check lock ordering w.r.t. > other lock types. > ISTR you had a much nicer version of this where you gave a custom order function -- what happend to that?