From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: <linux-kernel@vger.kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Anton Blanchard <anton@ozlabs.org>
Subject: [PATCH 0/2] trace/kprobe: Two fixes for kretprobes
Date: Mon, 14 Jun 2021 23:33:27 +0530 [thread overview]
Message-ID: <cover.1623693448.git.naveen.n.rao@linux.vnet.ibm.com> (raw)
The first patch fixes accounting of missed kretprobes in kprobe_profile.
The second patch removes limit on the maximum active kretprobe
instances, when registering a kretprobe through tracefs.
- Naveen
Naveen N. Rao (2):
trace/kprobe: Fix count of missed kretprobes in kprobe_profile
trace/kprobe: Remove limit on kretprobe maxactive
kernel/trace/trace_kprobe.c | 11 ++---------
kernel/trace/trace_probe.h | 1 -
.../ftrace/test.d/kprobe/kprobe_syntax_errors.tc | 1 -
.../ftrace/test.d/kprobe/kretprobe_maxactive.tc | 3 ---
4 files changed, 2 insertions(+), 14 deletions(-)
base-commit: 0b42677e2e5d87c730ddc41544b289b88596738c
--
2.31.1
next reply other threads:[~2021-06-14 18:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 18:03 Naveen N. Rao [this message]
2021-06-14 18:03 ` [PATCH 1/2] trace/kprobe: Fix count of missed kretprobes in kprobe_profile Naveen N. Rao
2021-06-15 5:47 ` Masami Hiramatsu
2021-06-14 18:03 ` [PATCH 2/2] trace/kprobe: Remove limit on kretprobe maxactive Naveen N. Rao
2021-06-15 9:35 ` Masami Hiramatsu
2021-06-15 17:41 ` Naveen N. Rao
2021-06-16 0:46 ` Masami Hiramatsu
2021-06-16 1:03 ` Steven Rostedt
2021-06-16 2:27 ` Masami Hiramatsu
2021-06-16 15:10 ` Masami Hiramatsu
2021-06-17 16:34 ` Naveen N. Rao
2021-06-17 17:07 ` Steven Rostedt
2021-06-18 4:26 ` Masami Hiramatsu
2021-06-18 8:41 ` Naveen N. Rao
2021-06-17 16:19 ` Naveen N. Rao
2021-06-18 6:17 ` Masami Hiramatsu
2021-06-18 13:19 ` Naveen N. Rao
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=cover.1623693448.git.naveen.n.rao@linux.vnet.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=anton@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).