All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <cl@linux.com>,
	Pekka Enberg <penberg@kernel.org>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	"Paul E . McKenney" <paulmck@kernel.org>,
	linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>,
	Oliver Glitta <glittao@gmail.com>
Subject: Re: [PATCH] [PATCH] mm, slub: enable slub_debug static key when creating cache with explicit debug flags
Date: Mon, 15 Mar 2021 18:28:42 +0100	[thread overview]
Message-ID: <e723d919-222a-0675-5aae-44dfe1ce005f@suse.cz> (raw)
In-Reply-To: <2d80f81a-ed85-a36f-6527-b75da3ae209e@google.com>

On 3/15/21 6:16 PM, David Rientjes wrote:
> On Mon, 15 Mar 2021, Vlastimil Babka wrote:
> 
>> Commit ca0cab65ea2b ("mm, slub: introduce static key for slub_debug()")
>> introduced a static key to optimize the case where no debugging is enabled for
>> any cache. The static key is enabled when slub_debug boot parameter is passed,
>> or CONFIG_SLUB_DEBUG_ON enabled.
>> 
>> However, some caches might be created with one or more debugging flags
>> explicitly passed to kmem_cache_create(), and the commit missed this. Thus the
>> debugging functionality would not be actually performed for these caches unless
>> the static key gets enabled by boot param or config.
>> 
>> This patch fixes it by checking for debugging flags passed to
>> kmem_cache_create() and enabling the static key accordingly.
>> 
>> Note such explicit debugging flags should not be used outside of debugging and
>> testing as they will now enable the static key globally. btrfs_init_cachep()
>> creates a cache with SLAB_RED_ZONE but that's a mistake that's being corrected
>> [1]. rcu_torture_stats() creates a cache with SLAB_STORE_USER, but that is a
>> testing module so it's OK and will start working as intended after this patch.
>> 
>> Also note that in case of backports to kernels before v5.12 that don't have
>> 59450bbc12be ("mm, slab, slub: stop taking cpu hotplug lock"),
>> static_branch_enable_cpuslocked() should be used.
>> 
> 
> Since this affects 5.9+, is the plan to propose backports to stable with 
> static_branch_enable_cpuslocked() once this is merged?  (I notice the 
> absence of the stable tag here, which I believe is intended.)

I was thinking about it, and since the rcutorture user is only in -next (AFAICS)
and btrfs user was unintended, it didn't seem to meet stable criteria to me. But
I won't mind if it's backported.

>> [1] https://lore.kernel.org/linux-btrfs/20210315141824.26099-1-dsterba@suse.com/
>> 
>> Reported-by: Oliver Glitta <glittao@gmail.com>
>> Fixes: ca0cab65ea2b ("mm, slub: introduce static key for slub_debug()")
>> Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
> 
> Acked-by: David Rientjes <rientjes@google.com>

Thanks!

>> ---
>>  mm/slub.c | 9 +++++++++
>>  1 file changed, 9 insertions(+)
>> 
>> diff --git a/mm/slub.c b/mm/slub.c
>> index 350a37f30e60..cd6694ad1a0a 100644
>> --- a/mm/slub.c
>> +++ b/mm/slub.c
>> @@ -3827,6 +3827,15 @@ static int calculate_sizes(struct kmem_cache *s, int forced_order)
>>  
>>  static int kmem_cache_open(struct kmem_cache *s, slab_flags_t flags)
>>  {
>> +#ifdef CONFIG_SLUB_DEBUG
>> +	/*
>> +	 * If no slub_debug was enabled globally, the static key is not yet
>> +	 * enabled by setup_slub_debug(). Enable it if the cache is being
>> +	 * created with any of the debugging flags passed explicitly.
>> +	 */
>> +	if (flags & SLAB_DEBUG_FLAGS)
>> +		static_branch_enable(&slub_debug_enabled);
>> +#endif
>>  	s->flags = kmem_cache_flags(s->size, flags, s->name);
>>  #ifdef CONFIG_SLAB_FREELIST_HARDENED
>>  	s->random = get_random_long();
> 


  reply	other threads:[~2021-03-15 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 15:34 [PATCH] [PATCH] mm, slub: enable slub_debug static key when creating cache with explicit debug flags Vlastimil Babka
2021-03-15 17:16 ` David Rientjes
2021-03-15 17:16   ` David Rientjes
2021-03-15 17:28   ` Vlastimil Babka [this message]
2021-03-15 17:32     ` Paul E. McKenney
2021-03-15 17:36       ` Vlastimil Babka
2021-03-15 17:59         ` Paul E. McKenney

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=e723d919-222a-0675-5aae-44dfe1ce005f@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=dsterba@suse.com \
    --cc=glittao@gmail.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=paulmck@kernel.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.