linux-kernel - Re: 回复: [PATCH] lockdep: Fix upper limit for LOCKDEP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z9w-MVjD4olLlKDa@google.com>
Date: Thu, 20 Mar 2025 16:11:29 +0000
From: Carlos Llamas <cmllamas@...gle.com>
To: "zhangxiaomeng (A)" <zhangxiaomeng13@...wei.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Boqun Feng <boqun.feng@...il.com>,
	"J. R. Okajima" <hooanon05g@...il.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Waiman Long <longman@...hat.com>, Ingo Molnar <mingo@...hat.com>,
	Will Deacon <will@...nel.org>
Subject: Re: 回复: [PATCH] lockdep: Fix upper
 limit for LOCKDEP_BITS configs

On Wed, Mar 19, 2025 at 09:48:11AM +0000, zhangxiaomeng (A) wrote:
> Thank you for the response. I should clarify that the issue occurs when modifying additional config values. Specifically, when LOCKDEP_BITS is set to 24 along with setting LOCKDEP_CHAINS_BITS and LOCKDEP_STACK_TRACE_BITS to their maximum upper limits, the build fails.

Right, that's what I figured. I don't know that bumping all these values
to their limit at once makes sense. I think allowing LOCKDEP_BITS to go
higher independently might still be useful so I don't see a reason to
change that.

--
Carlos Llamas