From: Steven Rostedt <srostedt@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH for tip] tracing: Don't use tracing_record_cmdline() in workqueue tracer fix
Date: Thu, 12 Mar 2009 20:48:08 -0400 [thread overview]
Message-ID: <1236905288.11290.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20090313090042.43CD.A69D9226@jp.fujitsu.com>
On Fri, 2009-03-13 at 09:03 +0900, KOSAKI Motohiro wrote:
> commit c3ffc7a40b7e94b094efe1c8ab4e24370a782b65 "Don't use tracing_record_cmdline()
> in workqueue tracer" have a race window.
>
> find_task_by_vpid() require task_list_lock(). but the patch doesn't.
>
> fixing here.
>
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> ---
Applied, thanks!
-- Steve
next prev parent reply other threads:[~2009-03-13 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 0:03 [PATCH for tip] tracing: Don't use tracing_record_cmdline() in workqueue tracer fix KOSAKI Motohiro
2009-03-13 0:48 ` Steven Rostedt [this message]
2009-03-13 4:03 ` [tip:tracing/ftrace] " KOSAKI Motohiro
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=1236905288.11290.5.camel@localhost.localdomain \
--to=srostedt@redhat.com \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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