All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: linux-kernel@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	yrl.pp-manager.tt@hitachi.com, Oleg Nesterov <oleg@redhat.com>,
	Ingo Molnar <mingo@redhat.com>,
	Tom Zanussi <tom.zanussi@intel.com>
Subject: [PATCH 0/3][BUGFIX] tracing/kprobe: memory barrier related bugfixes
Date: Mon, 13 May 2013 20:58:25 +0900	[thread overview]
Message-ID: <20130513115824.6545.47677.stgit@mhiramat-M0-7522> (raw)

Hi,

Here are three patches for fixing rcu memory barrier related issue
and sparse warnings, which I was made on previous series.

---

Masami Hiramatsu (3):
      [BUGFIX] tracing/kprobes: Use rcu_dereference_raw for tp->files
      [CLEANUP/SPARSE] tracing/kprobes: Fix a sparse warning for incorrect type in assignment
      [CLEANUP/SPARSE] tracing/kprobes: Make print_*probe_event static


 kernel/trace/trace_kprobe.c |   53 ++++++++++++++++++++++++++++++++-----------
 1 file changed, 40 insertions(+), 13 deletions(-)

-- 
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
IT Management Research Dept. and Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory

             reply	other threads:[~2013-05-13 12:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 11:58 Masami Hiramatsu [this message]
2013-05-13 11:58 ` [PATCH 1/3] [BUGFIX] tracing/kprobes: Use rcu_dereference_raw for tp->files Masami Hiramatsu
2013-05-13 11:58 ` [PATCH 2/3] [CLEANUP/SPARSE] tracing/kprobes: Fix a sparse warning for incorrect type in assignment Masami Hiramatsu
2013-05-13 11:58 ` [PATCH 3/3] [CLEANUP/SPARSE] tracing/kprobes: Make print_*probe_event static Masami Hiramatsu

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=20130513115824.6545.47677.stgit@mhiramat-M0-7522 \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=oleg@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=tom.zanussi@intel.com \
    --cc=yrl.pp-manager.tt@hitachi.com \
    --subject='Re: [PATCH 0/3][BUGFIX] tracing/kprobe: memory barrier related bugfixes' \
    /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

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.