From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 82F2AC433E0 for ; Mon, 15 Mar 2021 18:01:20 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 1C45C64E81 for ; Mon, 15 Mar 2021 18:01:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1C45C64E81 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 88CFD6B006C; Mon, 15 Mar 2021 14:01:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 83D246B0070; Mon, 15 Mar 2021 14:01:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 705176B0071; Mon, 15 Mar 2021 14:01:19 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0244.hostedemail.com [216.40.44.244]) by kanga.kvack.org (Postfix) with ESMTP id 569BD6B006C for ; Mon, 15 Mar 2021 14:01:19 -0400 (EDT) Received: from smtpin21.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 08C5B180AD830 for ; Mon, 15 Mar 2021 18:01:19 +0000 (UTC) X-FDA: 77922875478.21.07FBD5B Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf25.hostedemail.com (Postfix) with ESMTP id 9D01A6006133 for ; Mon, 15 Mar 2021 17:36:39 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 35D55AE8F; Mon, 15 Mar 2021 17:36:38 +0000 (UTC) Subject: Re: [PATCH] [PATCH] mm, slub: enable slub_debug static key when creating cache with explicit debug flags To: paulmck@kernel.org Cc: David Rientjes , Andrew Morton , Christoph Lameter , Pekka Enberg , Joonsoo Kim , linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org, David Sterba , Oliver Glitta References: <20210315153415.24404-1-vbabka@suse.cz> <2d80f81a-ed85-a36f-6527-b75da3ae209e@google.com> <20210315173207.GN2696@paulmck-ThinkPad-P72> From: Vlastimil Babka Message-ID: <8c4f3385-e935-8363-c6bd-ffe6b8c2d6c4@suse.cz> Date: Mon, 15 Mar 2021 18:36:34 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: <20210315173207.GN2696@paulmck-ThinkPad-P72> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Stat-Signature: on6wyxp1qbcqpzc44jxogktqb3qgobgf X-Rspamd-Server: rspam02 X-Rspamd-Queue-Id: 9D01A6006133 Received-SPF: none (suse.cz>: No applicable sender policy available) receiver=imf25; identity=mailfrom; envelope-from=""; helo=mx2.suse.de; client-ip=195.135.220.15 X-HE-DKIM-Result: none/none X-HE-Tag: 1615829799-848855 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 3/15/21 6:32 PM, Paul E. McKenney wrote: > On Mon, Mar 15, 2021 at 06:28:42PM +0100, Vlastimil Babka wrote: >> 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. > > I had better ask... Should rcutorture be doing something different? > > Thanx, Paul No, I think it's fine if a testing module such as rcutorture flips the static key for the rest of the kernel's uptime. I only CC'd you as FYI in case you were wondering why you can't see any alloc/free stacks in its output :)