From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
fweisbec@gmail.com, mingo@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3] tracing - avoid soft lockup in trace_pipe
Date: Fri, 25 Mar 2011 11:49:37 -0400 [thread overview]
Message-ID: <1301068177.14261.192.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20110325110518.GC1922@jolsa.brq.redhat.com>
On Fri, 2011-03-25 at 12:05 +0100, Jiri Olsa wrote:
> right, I'm now able to trigger the issue when running setting the tracing
> as said in the patch and plus running this in few instacies:
>
> (while [ 1 ]; do find / > /dev/null ; done) &
That didn't work for me either. But if I run hackbench 50 on the box,
then the trace does hang while it is running.
>
> It's strange I did not need this last time.. not sure why :)
>
>
> anyway, the original reproducer I picked this issue from is ltp suite:
> http://sourceforge.net/projects/ltp/files/LTP%20Source/ltp-20100131/ltp-full-20100131.tgz/download
>
> and running following test:
> ltp-full-20101031/testcases/kernel/tracing/ftrace_stress_test/ftrace_stress_test.sh
>
> reproduces the issue all the time for me, and the patch fixies it.
> Attaching patch rebased to the current master with changed comment.
Thanks, I'll queue it up for 2.6.40, as I do not think this is that
critical of a bug.
-- Steve
next prev parent reply other threads:[~2011-03-25 15:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 22:59 [PATCH 0/2] " Jiri Olsa
2011-03-12 22:59 ` [PATCH 1/2] tracing - trace lost events properly Jiri Olsa
2011-03-12 22:59 ` [PATCH 2/2] tracing - putting cond_resched into tace_pipe loop Jiri Olsa
2011-03-13 14:58 ` Oleg Nesterov
2011-03-14 14:07 ` Steven Rostedt
2011-03-14 14:18 ` Jiri Olsa
2011-03-14 14:28 ` Steven Rostedt
2011-03-14 15:07 ` Jiri Olsa
2011-03-14 15:20 ` Steven Rostedt
2011-03-14 18:06 ` [PATCHv2] tracing - avoid soft lockup in trace_pipe Jiri Olsa
2011-03-21 12:10 ` Jiri Olsa
2011-03-25 2:23 ` Steven Rostedt
2011-03-25 3:14 ` Steven Rostedt
2011-03-25 11:05 ` [PATCHv3] " Jiri Olsa
2011-03-25 15:46 ` Steven Rostedt
2011-03-25 15:49 ` Steven Rostedt [this message]
2011-03-25 15:53 ` Jiri Olsa
2011-04-27 15:22 ` [tip:perf/core] tracing: Avoid " tip-bot for Jiri Olsa
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=1301068177.14261.192.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
/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®