The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
	Peter Zijlstra <peterz@infradead.org>,
	Alexei Starovoitov <ast@kernel.org>,
	linux-mm@vger.kernel.org,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: debugobject: Make it work with deferred page initialization - again
Date: Wed, 24 Jun 2026 11:20:02 +0200	[thread overview]
Message-ID: <877bnol2gt.ffs@fw13> (raw)
In-Reply-To: <a9825502-fbb3-4a2a-91ab-b91755ab5ead@kernel.org>

On Tue, Jun 23 2026 at 22:50, Vlastimil Babka wrote:
> On 2/7/26 14:27, Thomas Gleixner wrote:
>> In preemptible context the reclaim bit is harmless and not a performance
>> issue as that's usually invoked from slow path initialization context.
>> 
>> That makes debugobjects depend on PREEMPT_COUNT || !DEFERRED_STRUCT_PAGE_INIT.
>> 
>> Fixes: af92793e52c3 ("slab: Introduce kmalloc_nolock() and kfree_nolock().")
>> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> FYI, it should now be possible to revert this workaround:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=335c347686e76df9d2c7d7f61b5ea627a4c5cb4c

Cool.

      reply	other threads:[~2026-06-24  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07 13:27 debugobject: Make it work with deferred page initialization - again Thomas Gleixner
2026-02-07 19:23 ` Alexei Starovoitov
2026-02-09 11:39 ` Vlastimil Babka
2026-02-10  7:37 ` Sebastian Andrzej Siewior
2026-02-10 10:51 ` [tip: core/debugobjects] " tip-bot2 for Thomas Gleixner
2026-02-10 13:10 ` tip-bot2 for Thomas Gleixner
2026-06-23 20:50 ` Vlastimil Babka (SUSE)
2026-06-24  9:20   ` Thomas Gleixner [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=877bnol2gt.ffs@fw13 \
    --to=tglx@kernel.org \
    --cc=ast@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=vbabka@kernel.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