From: Vlastimil Babka <vbabka@suse.cz>
To: Stephen Boyd <swboyd@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Petr Mladek <pmladek@suse.com>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH v3 4/4] slub: Force on no_hash_pointers when slub_debug is enabled
Date: Wed, 2 Jun 2021 12:48:49 +0200 [thread overview]
Message-ID: <8a464fef-0530-aebf-5844-c8aaf2bf6f37@suse.cz> (raw)
In-Reply-To: <CAE-0n50F0E706Hzu9KyR7+7NRG39f0Rn05XT9mi8ci8csenxtQ@mail.gmail.com>
On 6/2/21 3:03 AM, Stephen Boyd wrote:
> Quoting Andrew Morton (2021-06-01 17:26:59)
>> On Wed, 2 Jun 2021 06:45:55 +0800 kernel test robot <lkp@intel.com> wrote:
>>
>> > >> mm/slub.c:4464:30: error: use of undeclared identifier 'slub_debug_enabled'
>> > if (static_branch_unlikely(&slub_debug_enabled))
>> > ^
>> > >> mm/slub.c:4464:30: error: use of undeclared identifier 'slub_debug_enabled'
>> > >> mm/slub.c:4464:30: error: use of undeclared identifier 'slub_debug_enabled'
>> > >> mm/slub.c:4464:30: error: use of undeclared identifier 'slub_debug_enabled'
>> > >> mm/slub.c:4464:6: error: invalid argument type 'void' to unary expression
>> > if (static_branch_unlikely(&slub_debug_enabled))
>> > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> Thanks. Stephen, how about this?
>
> Looks good to me. Thanks for the quick fix!
>
>>
>> --- a/mm/slub.c~slub-force-on-no_hash_pointers-when-slub_debug-is-enabled-fix
>> +++ a/mm/slub.c
>> @@ -117,12 +117,26 @@
>> */
>>
>> #ifdef CONFIG_SLUB_DEBUG
>> +
>> #ifdef CONFIG_SLUB_DEBUG_ON
>> DEFINE_STATIC_KEY_TRUE(slub_debug_enabled);
>> #else
>> DEFINE_STATIC_KEY_FALSE(slub_debug_enabled);
>> #endif
>> -#endif
>> +
>> +static inline bool __slub_debug_enabled(void)
>> +{
>> + return static_branch_unlikely(&slub_debug_enabled);
>
> To make this even better it could be
>
> return static_branch_maybe(CONFIG_SLUB_DEBUG_ON, &slub_debug_enabled);
>
>> +}
>> +
>> +#else /* CONFIG_SLUB_DEBUG */
>> +
>> +static inline bool __slub_debug_enabled(void)
>> +{
>> + return false;
>> +}
>> +
>> +#endif /* CONFIG_SLUB_DEBUG */
>>
>> static inline bool kmem_cache_debug(struct kmem_cache *s)
>> {
>> @@ -4493,7 +4507,7 @@ void __init kmem_cache_init(void)
>> slub_max_order = 0;
>>
>> /* Print slub debugging pointers without hashing */
>> - if (static_branch_unlikely(&slub_debug_enabled))
>> + if (__slub_debug_enabled())
A minimal fix would be to put this under #ifdef CONFIG_SLUB_DEBUG
and use static_key_enabled() as we don't need the jump label optimization for
init code. But the current fix works.
>
> It would be super cool if static branches could be optimized out when
> they're never changed by any code, nor exported to code, just tested in
> conditions. I've no idea if that is the case though.
>
>> no_hash_pointers_enable(NULL);
>>
>> kmem_cache_node = &boot_kmem_cache_node;
>
next prev parent reply other threads:[~2021-06-02 15:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 18:21 [PATCH v3 0/4] slub: Print non-hashed pointers in slub debugging Stephen Boyd
2021-06-01 18:21 ` [PATCH v3 1/4] slub: Restore slub_debug=- behavior Stephen Boyd
2021-06-01 18:22 ` [PATCH v3 2/4] slub: Actually use 'message' in restore_bytes() Stephen Boyd
2021-06-01 18:22 ` [PATCH v3 3/4] slub: Indicate slab_fix() uses printf formats Stephen Boyd
2021-06-06 0:06 ` David Rientjes
2021-06-01 18:22 ` [PATCH v3 4/4] slub: Force on no_hash_pointers when slub_debug is enabled Stephen Boyd
2021-06-01 22:45 ` kernel test robot
2021-06-02 0:26 ` Andrew Morton
2021-06-02 1:03 ` Stephen Boyd
2021-06-02 10:48 ` Vlastimil Babka [this message]
2021-06-02 10:50 ` Vlastimil Babka
2021-06-03 13:15 ` Petr Mladek
2021-09-20 14:29 ` Kees Cook
2021-09-20 18:23 ` Stephen Boyd
2021-09-20 18:28 ` Kees Cook
2021-09-20 18:44 ` Stephen Boyd
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=8a464fef-0530-aebf-5844-c8aaf2bf6f37@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=joe@perches.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=penberg@kernel.org \
--cc=pmladek@suse.com \
--cc=rientjes@google.com \
--cc=swboyd@chromium.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
Powered by JetHome