From: Waiman Long <longman@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
Waiman Long <longman@redhat.com>
Subject: [PATCH v6 0/2] debugobjects: Don't call fill_pool() in early boot hardirq context
Date: Sun, 7 Jun 2026 22:22:20 -0400 [thread overview]
Message-ID: <20260608022222.723265-1-longman@redhat.com> (raw)
v6:
- Break the v5 patch into 2 separate patches with the first patch just
adding a can_fill_pool() helper with no functional change as
suggested by Ingo.
Patch 1 adds a can_fill_pool() helper to break down the conditional
check in debug_objects_fill_pool() to determine if fill_pool() should
be called into easier to read components.
Patch 2 fix the lockdep warning caused by calling fill_pool() in early
boot hardirq context.
These 2 patches together produce the same code change as in the v5 patch
[1]. So the Reviewed-by tag from Sebastian is kept in the patch 2.
[1] https://lore.kernel.org/lkml/20260605173038.495075-1-longman@redhat.com/
Waiman Long (2):
debugobjects: Add a can_fill_pool() helper for
debug_objects_fill_pool()
debugobjects: Don't call fill_pool() in early boot hardirq context
lib/debugobjects.c | 46 +++++++++++++++++++++++++++++++++++++---------
1 file changed, 37 insertions(+), 9 deletions(-)
--
2.54.0
next reply other threads:[~2026-06-08 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 2:22 Waiman Long [this message]
2026-06-08 2:22 ` [PATCH v6 1/2] debugobjects: Add a can_fill_pool() helper for debug_objects_fill_pool() Waiman Long
2026-06-08 2:22 ` [PATCH v6 2/2] debugobjects: Don't call fill_pool() in early boot hardirq context Waiman Long
2026-06-08 7:56 ` [PATCH v6 0/2] " Sebastian Andrzej Siewior
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=20260608022222.723265-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®