From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] lockdep: Do not record irq state in debug_check_no_locks_freed()
Date: Wed, 4 Apr 2018 18:23:05 +0200 [thread overview]
Message-ID: <20180404162305.GK4043@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180404121904.6713fb9d@gandalf.local.home>
On Wed, Apr 04, 2018 at 12:19:04PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt (VMware) <rostedt@goodmis.org>
>
> While debugging where things were going wrong with mapping
> enabling/disabling interrupts with the lockdep state and actual real
> enabling and disabling interrupts, I had to silent the irq
> disabling/enabling in debug_check_no_locks_freed() because it was
> always showing up as it was called before the splat was.
>
> Use raw_local_irq_save/restore() for debug_check_no_locks_freed() as it
> hides useful information about where interrupts were used incorrectly
> last.
>
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> ---
> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> index 89b5f83f1969..8c145dc1315b 100644
> --- a/kernel/locking/lockdep.c
> +++ b/kernel/locking/lockdep.c
> @@ -4407,7 +4407,7 @@ void debug_check_no_locks_freed(const void *mem_from, unsigned long mem_len)
> if (unlikely(!debug_locks))
> return;
>
> - local_irq_save(flags);
> + raw_local_irq_save(flags);
> for (i = 0; i < curr->lockdep_depth; i++) {
> hlock = curr->held_locks + i;
>
> @@ -4418,7 +4418,7 @@ void debug_check_no_locks_freed(const void *mem_from, unsigned long mem_len)
> print_freed_lock_bug(curr, mem_from, mem_from + mem_len, hlock);
> break;
> }
> - local_irq_restore(flags);
> + raw_local_irq_restore(flags);
> }
> EXPORT_SYMBOL_GPL(debug_check_no_locks_freed);
Makes sense, could you convert all of them just to make sure there
aren't any left?
next prev parent reply other threads:[~2018-04-04 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 16:19 Steven Rostedt
2018-04-04 16:23 ` Peter Zijlstra [this message]
2018-04-04 17:15 ` Steven Rostedt
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=20180404162305.GK4043@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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®