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: Two more small fixes
Date: Mon, 22 Feb 2016 10:22:42 -0500 [thread overview]
Message-ID: <20160222152242.720105385@goodmis.org> (raw)
Linus,
Two more small fixes.
One is by Yang Shi who added a READ_ONCE_NOCHECK() to the scan of the
stack made by the stack tracer. As the stack tracer scans the entire
kernel stack, KASAN triggers seeing it as a "stack out of bounds" error.
As the scan is looking at the contents of the stack from parent functions.
The NOCHECK() tells KASAN that this is done on purpose, and is not some
kind of stack overflow.
The second fix is to the ftrace selftests, to retrieve the PID of executed
commands from the shell with "$!" and not by parsing "jobs".
Please pull the latest trace-fixes-v4.5-rc5 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-fixes-v4.5-rc5
Tag SHA1: 8510e551f97e02f02e853685524e9da17d48cbff
Head SHA1: 6e22c8366416251a3d88ba6c92d13d595089f0ed
Steven Rostedt (1):
ftracetest: Fix instance test to use proper shell command for pids
Yang Shi (1):
tracing, kasan: Silence Kasan warning in check_stack of stack_tracer
----
kernel/trace/trace_stack.c | 6 +++++-
.../testing/selftests/ftrace/test.d/instances/instance.tc | 15 +++++----------
2 files changed, 10 insertions(+), 11 deletions(-)
next reply other threads:[~2016-02-22 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 15:22 Steven Rostedt [this message]
2016-02-22 15:22 ` [PATCH 1/2] ftracetest: Fix instance test to use proper shell command for pids Steven Rostedt
2016-02-22 15:22 ` [PATCH 2/2] tracing, kasan: Silence Kasan warning in check_stack of stack_tracer Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2017-04-20 13:58 [PATCH 0/2] [GIT PULL] tracing: Two more small fixes 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=20160222152242.720105385@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;
as well as URLs for NNTP newsgroup(s).