From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Dave Jones <davej@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: perf/ftrace lockup on 3.12-rc6 with trigger code
Date: Fri, 25 Oct 2013 12:19:43 +0200 [thread overview]
Message-ID: <20131025101943.GA3481@gmail.com> (raw)
In-Reply-To: <1382695687.12254.4.camel@pippen.local.home>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> > Urgh, I had turned those on to try to debug something and forgot
> > to disable. I feel like I saw this problem before I had those
> > enabled so I guess I have to start from scratch fuzzing to see
> > if I can get a more generally reproducible trace.
Btw., even if various config options are enabled, we don't want the
kernel to lock up. So it might not be _the_ bug you are looking, but
it certainly looks like _a_ bug.
> Looks like something is incorrectly enabling function tracer
> within perf. Peter told me that there's some ref count bug that
> may use data after being freed on exit.
>
> I tried the program that you attached in you previous email, and
> was not able to hit the bug. Are you able to hit the bug with that
> code each time?
A full .config and a SHA1 of the tested tree would definitely be
nice!
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-25 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 17:30 perf/ftrace lockup on 3.12-rc6 with trigger code Vince Weaver
2013-10-24 18:25 ` Vince Weaver
2013-10-25 10:08 ` Steven Rostedt
2013-10-25 10:19 ` Ingo Molnar [this message]
2013-10-25 13:17 ` Vince Weaver
2013-10-25 13:12 ` Vince Weaver
2013-10-25 21:36 ` Vince Weaver
2013-10-26 8:48 ` Ingo Molnar
2013-11-05 18:06 ` Vince Weaver
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=20131025101943.GA3481@gmail.com \
--to=mingo@kernel.org \
--cc=acme@ghostprotocols.net \
--cc=davej@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.weaver@maine.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.