[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161115142631.724209475@goodmis.org>
Date: Tue, 15 Nov 2016 09:26:31 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Alexei Starovoitov <ast@...nel.org>
Subject: [PATCH 0/2] [GIT PULL] ftrace: Add more checks to ignore disabled functions
Linus,
Alexei discovered a race condition in modules failing to load that
can cause a ftrace check to trigger and disable ftrace. This is because
of the way modules are registered to ftrace. Their functions are
loaded in the ftrace function tables but set to "disabled" since
they are still in the process of being loaded by the module. After
the module is finished, it calls back into the ftrace infrastructure
to enable it. Looking deeper into the locations that access all the
functions in the table, I found more locations that should ignore
the disabled ones.
Please pull the latest trace-v4.9-rc5 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.9-rc5
Tag SHA1: 0f6a062b1a2a55e2c0f801514e9f8792e4339aef
Head SHA1: 546fece4eae871f033925ccf0ff2b740725ae915
Alexei Starovoitov (1):
ftrace: Ignore FTRACE_FL_DISABLED while walking dyn_ftrace records
Steven Rostedt (Red Hat) (1):
ftrace: Add more checks for FTRACE_FL_DISABLED in processing ip records
----
kernel/trace/ftrace.c | 24 +++++++++++++++++++++++-
1 file changed, 23 insertions(+), 1 deletion(-)
Powered by blists - more mailing lists