From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] [GIT PULL] tracing: Simple fix and clean up for 5.0
Date: Mon, 04 Mar 2019 17:06:15 -0500 [thread overview]
Message-ID: <20190304220615.385873907@goodmis.org> (raw)
Linus,
This is a "pre-pull". It's only one small fix and one small clean up.
I'm testing a few small patches for my real pull request which will
come at a later time. The second patch depends on your tree anyway
so I included it along with the urgent fix.
A small fix Pavel sent me back in august was accidentally lost due to it
being placed with some other patches that failed some tests, and was rebased
out of my local tree. Which was a regression that caused event filters
not to handle negative numbers.
The clean up is from Masami that realized that the code in kprobes that
calls probe_mem_read() wrapper, which is to be used in code used by both
kprobes and uprobes, was only in code for kprobes. It should not use the
wrapper there, but instead call probe_kernel_read() directly.
Please pull the latest trace-v5.0-pre tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v5.0-pre
Tag SHA1: 6c5b335a8c8d7d98c09d10e15058f8325ff2cf9d
Head SHA1: 49ef5f45701c3dedc6aa6efee5d03756fea0f99d
Masami Hiramatsu (1):
tracing/kprobes: Use probe_kernel_read instead of probe_mem_read
Pavel Tikhomirov (1):
tracing: Fix event filters and triggers to handle negative numbers
----
kernel/trace/trace_events_filter.c | 5 ++++-
kernel/trace/trace_kprobe.c | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
next reply other threads:[~2019-03-04 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 22:06 Steven Rostedt [this message]
2019-03-04 22:06 ` [PATCH 1/2] tracing: Fix event filters and triggers to handle negative numbers Steven Rostedt
2019-03-04 22:06 ` [PATCH 2/2] tracing/kprobes: Use probe_kernel_read instead of probe_mem_read 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=20190304220615.385873907@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
/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