From: "Arend van Spriel" <arend@broadcom.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Oleg Nesterov" <oleg@redhat.com>,
"Masami Hiramatsu" <masami.hiramatsu.pt@hitachi.com>
Subject: Re: regression 3.11-rc1: rmmod hangs after tracing module
Date: Thu, 25 Jul 2013 10:32:08 +0200 [thread overview]
Message-ID: <51F0E288.80501@broadcom.com> (raw)
In-Reply-To: <1374605077.3356.128.camel@gandalf.local.home>
On 07/23/2013 08:44 PM, Steven Rostedt wrote:
> On Tue, 2013-07-23 at 20:07 +0200, Arend van Spriel wrote:
>> Hi Steven,
>>
>> During testing of our brcmfmac wireless driver I had a trace-cmd running
>> along (trace-cmd record -e brcmfmac:*). After the test I stopped the
>> trace, unplugged my usb device and did a rmmod resulting in the attached
>> lockdep splat. Hope you have an idea what is going wrong here.
>
> Thanks for the report!
>
> Does this fix you bug?
Thanks Steve,
Tested your patch and it indeed fixes my deadlock.
Regards,
Arend
> -- Steve
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 69cba47..882ec1d 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -1224,18 +1224,17 @@ void tracing_reset_current(int cpu)
> tracing_reset(&global_trace.trace_buffer, cpu);
> }
>
> +/* Must have trace_types_lock held */
> void tracing_reset_all_online_cpus(void)
> {
> struct trace_array *tr;
>
> - mutex_lock(&trace_types_lock);
> list_for_each_entry(tr, &ftrace_trace_arrays, list) {
> tracing_reset_online_cpus(&tr->trace_buffer);
> #ifdef CONFIG_TRACER_MAX_TRACE
> tracing_reset_online_cpus(&tr->max_buffer);
> #endif
> }
> - mutex_unlock(&trace_types_lock);
> }
>
> #define SAVED_CMDLINES 128
>
>
>
prev parent reply other threads:[~2013-07-25 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 18:07 regression 3.11-rc1: rmmod hangs after tracing module Arend van Spriel
2013-07-23 18:44 ` Steven Rostedt
2013-07-25 8:32 ` Arend van Spriel [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=51F0E288.80501@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=oleg@redhat.com \
--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