linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kumar, Kaushlendra" <kaushlendra.kumar@intel.com>
To: Harry Yoo <harry.yoo@oracle.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"vbabka@suse.cz" <vbabka@suse.cz>
Subject: RE: [PATCH] tools/mm/slabinfo: Fix trace disabling logic
Date: Mon, 8 Dec 2025 12:25:52 +0000	[thread overview]
Message-ID: <LV3PR11MB8768E870DF71EC1D14E5AA44F5A2A@LV3PR11MB8768.namprd11.prod.outlook.com> (raw)
In-Reply-To: <aTaajTO9QY4eSLR1@hyeyoo>

On Mon, Dec 08, 2025, Harry Hyeonggon Yoo wrote:
> On Mon, Dec 08, 2025 at 02:12:55PM +0530, Kaushlendra Kumar wrote:
>> When tracing is disabled (!tracing) but the slab has tracing enabled 
>> (s->trace), the code should disable tracing by writing 0, not enable 
>> it by writing 1. Fix the inverted logic to correctly turn off tracing.
>>
>> Signed-off-by: Kaushlendra Kumar <kaushlendra.kumar@intel.com>
>> ---
> 
> After commit 060807f841ac9 ("mm, slub: make remaining slub_debug related 
> attributes read-only"), enabling or disabling debug option at runtime is 
> not supported anymore. slabinfo's -d and -dA flags are not supposed work 
> on recent kernels.
> 
> As it turns out enabling or disabling debug features at runtime is not a 
> good idea anyway, could you please working on dropping the feature instead?

Thanks for the context. You're right-fixing inverted logic in code 
that's been non-functional since 060807f841ac9 doesn't add value.

I'll submit a cleanup series removing the obsolete 
runtime debug functionality:
- Remove -d/-dA options and related usage text
- Drop slab_debug() and set_obj() for debug attributes


-Kaushlendra


      reply	other threads:[~2025-12-08 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08  8:42 Kaushlendra Kumar
2025-12-08  9:29 ` Harry Yoo
2025-12-08 12:25   ` Kumar, Kaushlendra [this message]

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=LV3PR11MB8768E870DF71EC1D14E5AA44F5A2A@LV3PR11MB8768.namprd11.prod.outlook.com \
    --to=kaushlendra.kumar@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=harry.yoo@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    /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