linux-kernel - Re: [PATCH v2 1/3] 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 for Android: free password hash cracker in your pocket

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

Message-ID: <8552.1723261438@jrotkm2>
Date: Sat, 10 Aug 2024 12:43:58 +0900
From: hooanon05g@...il.com
To: Carlos Llamas <cmllamas@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
    linux-kernel@...r.kernel.org, kernel-team@...roid.com,
    Peter Zijlstra <peterz@...radead.org>,
    Boqun Feng <boqun.feng@...il.com>, Ingo Molnar <mingo@...hat.com>,
    Waiman Long <longman@...hat.com>, Will Deacon <will@...nel.org>
Subject: Re: [PATCH v2 1/3] lockdep: fix upper limit for LOCKDEP_*_BITS configs

Carlos Llamas:
> Yeah, I say that's expected if you bump these values to the max all at
> once. The values I gave were tested individually on top of the defconfig
> and boot completed fine (qemu x86_64 and aarch64 with -m 8G). I think
> it's fair to leave room to configure these knobs individually.

I see, understood.
Now you can freely add Acked-by from me.


J. R. Okajima