From: Ingo Molnar <mingo@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2 (repost)] locking/lockdep: add debug_show_all_lock_holders()
Date: Sat, 14 Jan 2023 10:36:00 +0100 [thread overview]
Message-ID: <Y8J3gAXLf4yc0FcL@gmail.com> (raw)
In-Reply-To: <41f43b27-d910-78e0-c0b3-f2885fe1cd22@I-love.SAKURA.ne.jp>
* Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> wrote:
> --- a/include/linux/debug_locks.h
> +++ b/include/linux/debug_locks.h
> @@ -48,7 +48,18 @@ extern int debug_locks_off(void);
> #endif
>
> #ifdef CONFIG_LOCKDEP
> -extern void debug_show_all_locks(void);
> +extern void __debug_show_all_locks(bool show_stack);
> +
> +static inline void debug_show_all_locks(void)
> +{
> + __debug_show_all_locks(false);
> +}
> +
> +static inline void debug_show_all_lock_holders(void)
> +{
> + __debug_show_all_locks(true);
> +}
> +
> extern void debug_show_held_locks(struct task_struct *task);
> extern void debug_check_no_locks_freed(const void *from, unsigned long len);
> extern void debug_check_no_locks_held(void);
> @@ -61,6 +72,10 @@ static inline void debug_show_held_locks(struct task_struct *task)
> {
> }
>
> +static inline void debug_show_all_lock_holders(void)
> +{
> +}
> +
> - debug_show_all_locks();
> + debug_show_all_lock_holders();
> -void debug_show_all_locks(void)
> +void __debug_show_all_locks(bool show_stack)
> {
> struct task_struct *g, *p;
>
> @@ -6495,12 +6496,19 @@ void debug_show_all_locks(void)
> pr_warn("INFO: lockdep is turned off.\n");
> return;
> }
> - pr_warn("\nShowing all locks held in the system:\n");
> + if (show_stack)
> + pr_warn("\nShowing all threads with locks held in the system:\n");
> + else
> + pr_warn("\nShowing all locks held in the system:\n");
>
> rcu_read_lock();
> for_each_process_thread(g, p) {
> if (!p->lockdep_depth)
> continue;
> + if (p == current && p->lockdep_depth == 1)
> + continue;
> + if (show_stack)
> + sched_show_task(p);
> lockdep_print_held_locks(p);
> touch_nmi_watchdog();
> touch_all_softlockup_watchdogs();
Yeah, so note how you introduce a function with a parameter:
void __debug_show_all_locks(bool show_stack)
... only to then *hide* the new parameter via helper functions:
static inline void debug_show_all_locks(void)
{
__debug_show_all_locks(false);
}
static inline void debug_show_all_lock_holders(void)
{
__debug_show_all_locks(true);
}
... which is a *strong* hint by our universe that the new parameter was
probably a bad idea to begin with.
Given how small debug_show_all_locks() is to begin with, I'd suggest simply
duplicating the loop into debug_show_all_lock_holders() or so.
Thanks,
Ingo
next prev parent reply other threads:[~2023-01-14 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 10:10 Tetsuo Handa
2022-12-29 0:25 ` Tetsuo Handa
2023-01-07 12:58 ` Tetsuo Handa
2023-01-14 9:36 ` Ingo Molnar [this message]
2023-01-14 9:53 ` Tetsuo Handa
2023-01-17 3:28 ` Waiman Long
2023-01-31 9:52 ` Tetsuo Handa
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=Y8J3gAXLf4yc0FcL@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
/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®