linux-kernel - Re: [PATCH v1 3/3] locking/lockdep,doc: Correct the max number of lock classes

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <93ccb871-7f57-9109-9072-8fc26f3b811c@redhat.com>
Date:   Sun, 11 Jul 2021 11:22:48 -0400
From:   Waiman Long <llong@...hat.com>
To:     Xiongwei Song <sxwjean@...com>, peterz@...radead.org,
        mingo@...hat.com, will@...nel.org, boqun.feng@...il.com
Cc:     linux-kernel@...r.kernel.org, Xiongwei Song <sxwjean@...il.com>,
        Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Subject: Re: [PATCH v1 3/3] locking/lockdep,doc: Correct the max number of
 lock classes

On 7/11/21 10:14 AM, Xiongwei Song wrote:
> From: Xiongwei Song <sxwjean@...il.com>
>
> The max number of lock classes is 8192.
>
> Signed-off-by: Xiongwei Song <sxwjean@...il.com>
> Cc: Jonathan Corbet <corbet@....net>
> Cc: linux-doc@...r.kernel.org
> ---
>   Documentation/locking/lockdep-design.rst | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/locking/lockdep-design.rst b/Documentation/locking/lockdep-design.rst
> index 82f36cab61bd..5c2dcec684ff 100644
> --- a/Documentation/locking/lockdep-design.rst
> +++ b/Documentation/locking/lockdep-design.rst
> @@ -341,7 +341,7 @@ Exceeding this number will trigger the following lockdep warning::
>   
>   	(DEBUG_LOCKS_WARN_ON(id >= MAX_LOCKDEP_KEYS))
>   
> -By default, MAX_LOCKDEP_KEYS is currently set to 8191, and typical
> +By default, MAX_LOCKDEP_KEYS is currently set to 8192, and typical
>   desktop systems have less than 1,000 lock classes, so this warning
>   normally results from lock-class leakage or failure to properly
>   initialize locks.  These two problems are illustrated below:
> @@ -383,7 +383,7 @@ you the number of lock classes currently in use along with the maximum::
>   
>   This command produces the following output on a modest system::
>   
> -	lock-classes:                          748 [max: 8191]
> +	lock-classes:                          748 [max: 8192]
>   
>   If the number allocated (748 above) increases continually over time,
>   then there is likely a leak.  The following command can be used to

Acked-by: Waiman Long <longman@...hat.com>