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 84DB7C05027 for ; Fri, 27 Jan 2023 00:21:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232563AbjA0AVv (ORCPT ); Thu, 26 Jan 2023 19:21:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57198 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229727AbjA0AVr (ORCPT ); Thu, 26 Jan 2023 19:21:47 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 479E67280 for ; Thu, 26 Jan 2023 16:20:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1674778830; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=eU69JRvJMCkqKVDkC+A6LiHt+DPJENzucWZepo2NoXY=; b=OWu35ePMOQmJrwy7qXhjbmtZDT13j8diQlKkUgFxXAzkS055K6Sm7k0M5znkKLWDfbWMla 8Y3rx3nBXdP6L7+iBJqm3X5FnRwCrfHc8sHK2AR28XfqjoEXD/rQfe1ZecJILP4cz9q8gQ BRAl+l5dxEMLa+xmq9E7dfCBBYGb9O0= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-345-ak2sVfZHN7GyERjEH34m9Q-1; Thu, 26 Jan 2023 19:20:26 -0500 X-MC-Unique: ak2sVfZHN7GyERjEH34m9Q-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 2E2E81991C42; Fri, 27 Jan 2023 00:20:26 +0000 (UTC) Received: from [10.22.33.13] (unknown [10.22.33.13]) by smtp.corp.redhat.com (Postfix) with ESMTP id B69F8C15BA0; Fri, 27 Jan 2023 00:20:25 +0000 (UTC) Message-ID: Date: Thu, 26 Jan 2023 19:20:25 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: Re: BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! Content-Language: en-US To: Mikhail Gavrilov , Boqun Feng Cc: dsterba@suse.cz, Btrfs BTRFS , Linux List Kernel Mailing , Chris Murphy , Peter Zijlstra , Ingo Molnar , Will Deacon , Joel Fernandes References: <20220726164250.GE13489@twin.jikos.cz> <20230125171517.GV11562@twin.jikos.cz> From: Waiman Long In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/26/23 17:42, Mikhail Gavrilov wrote: >> I'm not sure whether these options are better than just increasing the >> number, maybe to unblock your ASAP, you can try make it 30 and make sure >> you have large enough memory to test. > About just to increase the LOCKDEP_CHAINS_BITS by 1. Where should this > be done? In vanilla kernel on kernel.org? In a specific distribution? > or the user must rebuild the kernel himself? Maybe increase > LOCKDEP_CHAINS_BITS by 1 is most reliable solution, but it difficult > to distribute to end users because the meaning of using packaged > distributions is lost (user should change LOCKDEP_CHAINS_BITS in > config and rebuild the kernel by yourself). Note that lockdep is typically only enabled in a debug kernel shipped by a distro because of the high performance overhead. The non-debug kernel doesn't have lockdep enabled. When LOCKDEP_CHAINS_BITS isn't big enough when testing on the debug kernel, you can file a ticket to the distro asking for an increase in CONFIG_LOCKDEP_CHAIN_BITS. Or you can build your own debug kernel with a bigger CONFIG_LOCKDEP_CHAIN_BITS. Cheers, Longman