From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
linux-trace-kernel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: [PATCH v5 0/5] tracing/probes: Fix bugs in process_fetch_insn
Date: Tue, 11 Jul 2023 23:15:20 +0900 [thread overview]
Message-ID: <168908491977.123124.16583481716284477889.stgit@devnote2> (raw)
Hi,
Here are the 5th version of fix bugs in process_fetch_insn_*().
The previous version is here;
https://lore.kernel.org/all/168904147563.2908673.18054267804278861545.stgit@mhiramat.roam.corp.google.com/
In this version I added a bugfix to update dynamic data counter only
if the fetcharg uses it [3/5] and update [5/5] to move out the arg->dynamic
check out from unlikely() macro and use likely() macro correctly for
non-error case.
Thank you,
---
Masami Hiramatsu (Google) (5):
tracing/probes: Fix to avoid double count of the string length on the array
tracing/probes: Fix not to count error code to total length
tracing/probes: Fix to update dynamic data counter if fetcharg uses it
Revert "tracing: Add "(fault)" name injection to kernel probes"
tracing/probes: Fix to record 0-length data_loc in fetch_store_string*() if fails
kernel/trace/trace.h | 2 ++
kernel/trace/trace_probe.c | 2 +-
kernel/trace/trace_probe_kernel.h | 30 ++++++++----------------------
kernel/trace/trace_probe_tmpl.h | 10 +++++-----
kernel/trace/trace_uprobe.c | 3 ++-
5 files changed, 18 insertions(+), 29 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2023-07-11 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 14:15 Masami Hiramatsu (Google) [this message]
2023-07-11 14:15 ` [PATCH v5 1/5] tracing/probes: Fix to avoid double count of the string length on the array Masami Hiramatsu (Google)
2023-07-11 14:15 ` [PATCH v5 2/5] tracing/probes: Fix not to count error code to total length Masami Hiramatsu (Google)
2023-07-11 14:15 ` [PATCH v5 3/5] tracing/probes: Fix to update dynamic data counter if fetcharg uses it Masami Hiramatsu (Google)
2023-07-13 13:34 ` Steven Rostedt
2023-07-13 14:34 ` Masami Hiramatsu
2023-07-11 14:15 ` [PATCH v5 4/5] Revert "tracing: Add "(fault)" name injection to kernel probes" Masami Hiramatsu (Google)
2023-07-11 16:19 ` Steven Rostedt
2023-07-11 14:16 ` [PATCH v5 5/5] tracing/probes: Fix to record 0-length data_loc in fetch_store_string*() if fails Masami Hiramatsu (Google)
2023-07-11 16:22 ` 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=168908491977.123124.16583481716284477889.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.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).