From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Miroslav Benes <mbenes@suse.cz>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jiri Kosina <jikos@kernel.org>, Petr Mladek <pmladek@suse.com>
Subject: [for-linus][PATCH 0/3] tracing/ftrace: trace_printk buffer fix and ftrace recursion fixes
Date: Sat, 31 Oct 2020 09:06:42 -0400 [thread overview]
Message-ID: <20201031130642.971173960@goodmis.org> (raw)
The indexing of the different context buffers had an off by one error.
The recursion protection for ftrace callbacks had two bugs.
One that would make NMIs always appear to be recursing
The other is trasitions between interrupt context could also cause
false positives and miss tracing those functions.
Qiujun Huang (1):
tracing: Fix out of bounds write in get_trace_buf
Steven Rostedt (VMware) (2):
ftrace: Fix recursion check for NMI test
ftrace: Handle tracing when switching between context
----
kernel/trace/trace.c | 2 +-
kernel/trace/trace.h | 26 +++++++++++++++++++++++---
kernel/trace/trace_selftest.c | 9 +++++++--
3 files changed, 31 insertions(+), 6 deletions(-)
next reply other threads:[~2020-10-31 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 13:06 Steven Rostedt [this message]
2020-10-31 13:06 ` [for-linus][PATCH 1/3] tracing: Fix out of bounds write in get_trace_buf Steven Rostedt
2020-10-31 13:06 ` [for-linus][PATCH 2/3] ftrace: Fix recursion check for NMI test Steven Rostedt
2020-10-31 13:06 ` [for-linus][PATCH 3/3] ftrace: Handle tracing when switching between context 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=20201031130642.971173960@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@kernel.org \
--cc=pmladek@suse.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