From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [for-next][PATCH 15/21] ftrace/kprobe: Show the maxactive number on kprobe_events
Date: Tue, 31 Mar 2020 13:11:23 +0000 [thread overview]
Message-ID: <20200331131124.5C1ED20784@mail.kernel.org> (raw)
In-Reply-To: <20200329184317.641598238@goodmis.org>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 696ced4fb1d7 ("tracing/kprobes: expose maxactive for kretprobe in kprobe_events").
The bot has tested the following trees: v5.5.13, v5.4.28, v4.19.113, v4.14.174.
v5.5.13: Build OK!
v5.4.28: Build OK!
v4.19.113: Failed to apply! Possible dependencies:
533059281ee5 ("tracing: probeevent: Introduce new argument fetching code")
56de76305279 ("tracing: probeevent: Cleanup print argument functions")
60c2e0cebfd0 ("tracing: probeevent: Add symbol type")
6212dd29683e ("tracing/kprobes: Use dyn_event framework for kprobe events")
a1303af5d79e ("tracing: probeevent: Add $argN for accessing function args")
b55ce203a8f3 ("tracing/probe: Add probe event name and group name accesses APIs")
f451bc89d835 ("tracing: probeevent: Unify fetch type tables")
v4.14.174: Failed to apply! Possible dependencies:
0b4c6841fee0 ("bpf: use the same condition in perf event set/free bpf handler")
43fa87f7deed ("perf/core: Fix another perf,trace,cpuhp lock inversion")
45408c4f9250 ("tracing: kprobes: Prohibit probing on notrace function")
4bebdc7a85aa ("bpf: add helper bpf_perf_prog_read_value")
533059281ee5 ("tracing: probeevent: Introduce new argument fetching code")
60c2e0cebfd0 ("tracing: probeevent: Add symbol type")
6212dd29683e ("tracing/kprobes: Use dyn_event framework for kprobe events")
908432ca84fc ("bpf: add helper bpf_perf_event_read_value for perf event array map")
97562633bcba ("bpf: perf event change needed for subsequent bpf helpers")
9802d86585db ("bpf: add a bpf_override_function helper")
a1303af5d79e ("tracing: probeevent: Add $argN for accessing function args")
b4da3340eae2 ("tracing/kprobe: bpf: Check error injectable event is on function entry")
b55ce203a8f3 ("tracing/probe: Add probe event name and group name accesses APIs")
d899926f552b ("selftest/ftrace: Move kprobe selftest function to separate compile unit")
dd0bb688eaa2 ("bpf: add a bpf_override_function helper")
de8f3a83b0a0 ("bpf: add meta pointer for direct access")
e12f03d7031a ("perf/core: Implement the 'perf_kprobe' PMU")
f3edacbd697f ("bpf: Revert bpf_overrid_function() helper changes.")
f451bc89d835 ("tracing: probeevent: Unify fetch type tables")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-03-31 13:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 18:42 [for-next][PATCH 00/21] tracing: Updates for v5.7 Steven Rostedt
2020-03-29 18:42 ` [for-next][PATCH 01/21] tracing: Use address-of operator on section symbols Steven Rostedt
2020-03-29 18:42 ` [for-next][PATCH 02/21] selftest/ftrace: Fix function trigger test to handle trace not disabling the tracer Steven Rostedt
2020-03-29 18:42 ` [for-next][PATCH 03/21] tracing: Save off entry when peeking at next entry Steven Rostedt
2020-03-29 18:42 ` [for-next][PATCH 04/21] ring-buffer: Have ring_buffer_empty() not depend on tracing stopped Steven Rostedt
2020-03-29 18:42 ` [for-next][PATCH 05/21] ring-buffer: Rename ring_buffer_read() to read_buffer_iter_advance() Steven Rostedt
2020-03-29 18:42 ` [for-next][PATCH 06/21] ring-buffer: Add page_stamp to iterator for synchronization Steven Rostedt
2020-03-29 18:42 ` [for-next][PATCH 07/21] ring-buffer: Have rb_iter_head_event() handle concurrent writer Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 08/21] ring-buffer: Do not die if rb_iter_peek() fails more than thrice Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 09/21] ring-buffer: Optimize rb_iter_head_event() Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 10/21] ring-buffer: Make resize disable per cpu buffer instead of total buffer Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 11/21] ring-buffer: Do not disable recording when there is an iterator Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 12/21] tracing: Do not disable tracing when reading the trace file Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 13/21] ring-buffer/tracing: Have iterator acknowledge dropped events Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 14/21] tracing: Have the document reflect that the trace file keeps tracing enabled Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 15/21] ftrace/kprobe: Show the maxactive number on kprobe_events Steven Rostedt
2020-03-31 13:11 ` Sasha Levin [this message]
2020-03-29 18:43 ` [for-next][PATCH 16/21] ftrace: Make function trace pid filtering a bit more exact Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 17/21] ftrace: Create set_ftrace_notrace_pid to not trace tasks Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 18/21] tracing: Create set_event_notrace_pid " Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 19/21] selftests/ftrace: Add test to test new set_ftrace_notrace_pid file Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 20/21] selftests/ftrace: Add test to test new set_event_notrace_pid file Steven Rostedt
2020-03-29 18:43 ` [for-next][PATCH 21/21] tracing: Add documentation on set_ftrace_notrace_pid and set_event_notrace_pid 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=20200331131124.5C1ED20784@mail.kernel.org \
--to=sashal@kernel.org \
--cc=mingo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.