From: Tom Zanussi <tom.zanussi@xxxxxxxxxxxxxxx> Hi Steve, Here's a fix for a problem I found with the hist trigger snapshot action related to the refactoring in the later versions of the patchset ('[PATCH 3/3] tracing: Add a check_val() check before updating cond_snapshot() track_val'). I also added v2 of 2 other patches that I previously submitted [1] but realized hadn't gotten picked up. ('[PATCH v2 1/3] tracing: Prevent hist_field_var_ref() from accessing NULL tracing_map_elts' and '[PATCH v2 2/3] tracing: Check keys for variable references in expressions too'). One of them I had to rebase ('[PATCH v2 2/3] tracing: Check keys for variable references in expressions too') because of the error_log changes since then, but the original ones still apply to versions before that). So in summary, all of these patches apply to current ftrace/core, while only '[PATCH 3/3] tracing: Add a check_val() check before updating cond_snapshot() track_val' and the previous 2 original patches in [1] apply to mainline. Thanks, Tom [1] https://lore.kernel.org/lkml/cover.1541687121.git.tom.zanussi@xxxxxxxxxxxxxxx/ The following changes since commit c8faaa4c594f55ddf903d61180029a3ea1da5286: rcu: validate arguments for rcu tracepoints (2019-04-03 08:26:38 -0400) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/zanussi/linux-trace.git ftrace/key-ref-fix-v2 Tom Zanussi (3): tracing: Prevent hist_field_var_ref() from accessing NULL tracing_map_elts tracing: Check keys for variable references in expressions too tracing: Add a check_val() check before updating cond_snapshot() track_val kernel/trace/trace_events_hist.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) -- 2.14.1