Oleg has been continuing his work on fixing a race between opening an
event file and deleting that same event. Using the i_private and event_mutex
to verify that the event still exists to solve the race.
A long standing bug on the ftrace hash accounting has finally been figured
out. When tracing a module that is removed and then reloaded, the function
filter hash gets out of sync with the function record's ref count which
causes a nasty warning and disabling of the function tracer.
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 6fd52fce057b55cc1bba463e6f05536a76c058b4
Oleg Nesterov (6):
tracing: Turn event/id->i_private into call->event.type
tracing: Change event_enable/disable_read() to verify i_private != NULL
tracing: Change event_filter_read/write to verify i_private != NULL
tracing: Change f_start() to take event_mutex and verify i_private != NULL
tracing: Introduce remove_event_file_dir()
tracing: Change remove_event_file_dir() to clear "d_subdirs"->i_private
Steven Rostedt (Red Hat) (2):
ftrace: Consolidate some duplicate code for updating ftrace ops
ftrace: Clear module traced functions on unload module
----
kernel/trace/ftrace.c | 76 +++++++++++++++--
kernel/trace/trace_events.c | 159 ++++++++++++++++++++----------------
kernel/trace/trace_events_filter.c | 17 ++--
3 files changed, 164 insertions(+), 88 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
