From: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Cc: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
Ingo Molnar <mingo@redhat.com>,
yrl.pp-manager.tt@hitachi.com
Subject: [PATCH ftrace/core 0/3] ftrace: Fix three small bugs
Date: Fri, 06 Jun 2014 07:35:15 +0900 [thread overview]
Message-ID: <20140605223515.32311.71203.stgit@yunodevel> (raw)
Hi Steven,
I found three small bugs for current ftrace/core, so I fixed those.
Would you apply these patches?
Thanks!
---
Yoshihiro YUNOMAE (3):
trace/event: Return error if ftrace_trace_arrays is empty list
trace/kprobes: Avoid self tests if tracing is disabled on boot up
trace: Fix memory leak when new instance creation failed
kernel/trace/trace.c | 23 ++++++++++++++---------
kernel/trace/trace.h | 3 +++
kernel/trace/trace_events.c | 13 +++++++++++++
kernel/trace/trace_kprobe.c | 3 +++
4 files changed, 33 insertions(+), 9 deletions(-)
--
Yoshihiro YUNOMAE
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: yoshihiro.yunomae.ez@hitachi.com
next reply other threads:[~2014-06-05 22:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 22:35 Yoshihiro YUNOMAE [this message]
2014-06-05 22:35 ` [PATCH ftrace/core 1/3] trace/event: Return error if ftrace_trace_arrays is empty list Yoshihiro YUNOMAE
2014-06-06 3:46 ` Steven Rostedt
2014-06-06 6:28 ` [PATCH ftrace/core] tracing: Remove return value in event_trace_self_tests() when top_trace_array() returns NULL Yoshihiro YUNOMAE
2014-06-06 6:31 ` Yoshihiro YUNOMAE
2014-06-06 8:45 ` Steven Rostedt
2014-06-05 22:35 ` [PATCH ftrace/core 2/3] trace/kprobes: Avoid self tests if tracing is disabled on boot up Yoshihiro YUNOMAE
2014-06-06 1:01 ` Masami Hiramatsu
2014-06-05 22:35 ` [PATCH ftrace/core 3/3] trace: Fix memory leak when new instance creation failed Yoshihiro YUNOMAE
2014-06-06 3:54 ` Steven Rostedt
2014-06-06 4:07 ` 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=20140605223515.32311.71203.stgit@yunodevel \
--to=yoshihiro.yunomae.ez@hitachi.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=yrl.pp-manager.tt@hitachi.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