From: Waiman Long <longman@redhat.com>
To: Carlos Llamas <cmllamas@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
"J. R. Okajima" <hooanon05g@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH 1/3] lockdep: fix upper limit for LOCKDEP_*_BITS configs
Date: Mon, 5 Aug 2024 21:29:45 -0400 [thread overview]
Message-ID: <0299406c-b316-4e79-848d-b6641dda0031@redhat.com> (raw)
In-Reply-To: <20240806010128.402852-2-cmllamas@google.com>
On 8/5/24 21:01, Carlos Llamas wrote:
> Lockdep has a set of configs used to determine the size of the static
> arrays that it uses. However, the upper limit that was initially setup
> for these configs is too high (30 bit shift). This equates to several
> GiB of static memory for individual symbols. Using such high values
> leads to linker errors:
>
> $ make defconfig
> $ ./scripts/config -e PROVE_LOCKING --set-val LOCKDEP_BITS 30
> $ make olddefconfig all
> [...]
> ld: kernel image bigger than KERNEL_IMAGE_SIZE
> ld: section .bss VMA wraps around address space
>
> Adjust the upper limits to the maximum values that avoid these issues.
> The need for anything more, likely points to a problem elsewhere. Note
> that LOCKDEP_CHAINS_BITS was intentionally left out as its upper limit
> had a different symptom and has already been fixed [1].
>
> Reported-by: J. R. Okajima <hooanon05g@gmail.com>
> Closes: https://lore.kernel.org/all/30795.1620913191@jrobl/ [1]
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Boqun Feng <boqun.feng@gmail.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Waiman Long <longman@redhat.com>
> Cc: Will Deacon <will@kernel.org>
> Signed-off-by: Carlos Llamas <cmllamas@google.com>
> ---
> lib/Kconfig.debug | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index a81d452941ce..baaaedfde0cb 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1507,7 +1507,7 @@ config LOCKDEP_SMALL
> config LOCKDEP_BITS
> int "Bitsize for MAX_LOCKDEP_ENTRIES"
> depends on LOCKDEP && !LOCKDEP_SMALL
> - range 10 30
> + range 10 24
> default 15
> help
> Try increasing this value if you hit "BUG: MAX_LOCKDEP_ENTRIES too low!" message.
> @@ -1523,7 +1523,7 @@ config LOCKDEP_CHAINS_BITS
> config LOCKDEP_STACK_TRACE_BITS
> int "Bitsize for MAX_STACK_TRACE_ENTRIES"
> depends on LOCKDEP && !LOCKDEP_SMALL
> - range 10 30
> + range 10 26
> default 19
> help
> Try increasing this value if you hit "BUG: MAX_STACK_TRACE_ENTRIES too low!" message.
> @@ -1531,7 +1531,7 @@ config LOCKDEP_STACK_TRACE_BITS
> config LOCKDEP_STACK_TRACE_HASH_BITS
> int "Bitsize for STACK_TRACE_HASH_SIZE"
> depends on LOCKDEP && !LOCKDEP_SMALL
> - range 10 30
> + range 10 26
> default 14
> help
> Try increasing this value if you need large STACK_TRACE_HASH_SIZE.
> @@ -1539,7 +1539,7 @@ config LOCKDEP_STACK_TRACE_HASH_BITS
> config LOCKDEP_CIRCULAR_QUEUE_BITS
> int "Bitsize for elements in circular_queue struct"
> depends on LOCKDEP
> - range 10 30
> + range 10 26
> default 12
> help
> Try increasing this value if you hit "lockdep bfs error:-1" warning due to __cq_enqueue() failure.
I agree that we should further limit the max values.
Acked-by: Waiman Long <longman@redhat.com>
next prev parent reply other threads:[~2024-08-06 1:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 1:01 [PATCH 0/3] lockdep: minor config and documentation fixes Carlos Llamas
2024-08-06 1:01 ` [PATCH 1/3] lockdep: fix upper limit for LOCKDEP_*_BITS configs Carlos Llamas
2024-08-06 1:29 ` Waiman Long [this message]
2024-08-06 1:01 ` [PATCH 2/3] lockdep: clarify size " Carlos Llamas
2024-08-06 1:36 ` Waiman Long
2024-08-06 14:47 ` Carlos Llamas
2024-08-06 14:52 ` Waiman Long
2024-08-06 17:42 ` Boqun Feng
2024-08-07 14:28 ` Carlos Llamas
2024-08-06 1:01 ` [PATCH 3/3] lockdep: document MAX_LOCKDEP_CHAIN_HLOCKS calculation Carlos Llamas
2024-08-06 1:27 ` Waiman Long
2024-08-06 14:49 ` Carlos Llamas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0299406c-b316-4e79-848d-b6641dda0031@redhat.com \
--to=longman@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=cmllamas@google.com \
--cc=hooanon05g@gmail.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®