From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
linux-trace-kernel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 4/4] tracing/probes: Fix to record 0-length data_loc in fetch_store_string*() if fails
Date: Mon, 10 Jul 2023 23:34:00 -0400 [thread overview]
Message-ID: <20230710233400.5aaf024e@gandalf.local.home> (raw)
In-Reply-To: <168904151104.2908673.8401909922292791503.stgit@mhiramat.roam.corp.google.com>
On Tue, 11 Jul 2023 11:11:51 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> --- a/kernel/trace/trace_probe_tmpl.h
> +++ b/kernel/trace/trace_probe_tmpl.h
> @@ -267,9 +267,7 @@ store_trace_args(void *data, struct trace_probe *tp, void *rec,
> if (unlikely(arg->dynamic))
> *dl = make_data_loc(maxlen, dyndata - base);
> ret = process_fetch_insn(arg->code, rec, dl, base);
> - if (unlikely(ret < 0 && arg->dynamic)) {
> - *dl = make_data_loc(0, dyndata - base);
> - } else {
> + if (unlikely(ret > 0 && arg->dynamic)) {
To match the current code, that should be:
if (likely(ret >= 0 || !arg->dynamic)) {
But I'm guessing that the original code was buggy, as the else block should
only have been processed if arg->dynamic was set? That is, it should have been:
if (arg->dynamic) {
if (unlikely(ret < 0)) {
*dl = make_data_loc(0, dyndata - base);
} else {
dyndata += ret;
maxlen -= ret;
}
}
I guess you only want to update if arg->dynamic is true (even though that
wasn't the case before :-/) But in any case, I think you want likely() and
not unlikely().
if (arg->dynamic && likely(ret > 0)) {
That is, if we only want to updated this if the arg is dynamic.
And I don't think that the arg->dynamic() should have likely/unlikely
around it, as that's determined by user space, and the kernel should not be
adding assumptions about what user space wants.
-- Steve
> dyndata += ret;
> maxlen -= ret;
> }
next prev parent reply other threads:[~2023-07-11 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 2:11 [PATCH v4 0/4] tracing/probes: Fix bugs in process_fetch_insn Masami Hiramatsu (Google)
2023-07-11 2:11 ` [PATCH v4 1/4] tracing/probes: Fix to avoid double count of the string length on the array Masami Hiramatsu (Google)
2023-07-11 2:11 ` [PATCH v4 2/4] tracing/probes: Fix not to count error code to total length Masami Hiramatsu (Google)
2023-07-11 2:11 ` [PATCH v4 3/4] Revert "tracing: Add "(fault)" name injection to kernel probes" Masami Hiramatsu (Google)
2023-07-11 2:11 ` [PATCH v4 4/4] tracing/probes: Fix to record 0-length data_loc in fetch_store_string*() if fails Masami Hiramatsu (Google)
2023-07-11 3:34 ` Steven Rostedt [this message]
2023-07-11 4:56 ` Masami Hiramatsu
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=20230710233400.5aaf024e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox