From: "Carlos López" <clopez@suse.de>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Alan Maguire <alan.maguire@oracle.com>,
"open list:TRACING" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing/probes: fix error check in parse_btf_field()
Date: Sun, 26 May 2024 14:27:56 +0200 [thread overview]
Message-ID: <ff240b23-4143-4171-8dcc-1fdbf1802e8c@suse.de> (raw)
In-Reply-To: <20240526191708.860651c915600a535cc2e579@kernel.org>
Hi,
On 26/5/24 12:17, Masami Hiramatsu (Google) wrote:
> On Sat, 25 May 2024 20:21:32 +0200
> Carlos López <clopez@suse.de> wrote:
>
>> btf_find_struct_member() might return NULL or an error via the
>> ERR_PTR() macro. However, its caller in parse_btf_field() only checks
>> for the NULL condition. Fix this by using IS_ERR() and returning the
>> error up the stack.
>>
>
> Thanks for finding it!
> I think this requires new error message for error_log file.
> Can you add the log as
>
> trace_probe_log_err(ctx->offset, BTF_ERROR);
>
> And define BTF_ERROR in ERRORS@kernel/trace/trace_probe.h ?
Sounds good, but should we perhaps reuse BAD_BTF_TID?
```
C(BAD_BTF_TID, "Failed to get BTF type info."),\
```
`btf_find_struct_member()` fails if `type` is not a struct or if it runs
OOM while allocating the anon stack, so it seems appropriate.
Best,
Carlos
> Thank you,
>
>> Fixes: c440adfbe3025 ("tracing/probes: Support BTF based data structure field access")
>> Signed-off-by: Carlos López <clopez@suse.de>
>> ---
>> kernel/trace/trace_probe.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/kernel/trace/trace_probe.c b/kernel/trace/trace_probe.c
>> index 5e263c141574..5417e9712157 100644
>> --- a/kernel/trace/trace_probe.c
>> +++ b/kernel/trace/trace_probe.c
>> @@ -554,6 +554,8 @@ static int parse_btf_field(char *fieldname, const struct btf_type *type,
>> anon_offs = 0;
>> field = btf_find_struct_member(ctx->btf, type, fieldname,
>> &anon_offs);
>> + if (IS_ERR(field))
>> + return PTR_ERR(field);
>> if (!field) {
>> trace_probe_log_err(ctx->offset, NO_BTF_FIELD);
>> return -ENOENT;
>> --
>> 2.35.3
>>
>
>
--
Carlos López
Security Engineer
SUSE Software Solutions
next prev parent reply other threads:[~2024-05-26 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 18:21 Carlos López
2024-05-26 10:17 ` Masami Hiramatsu
2024-05-26 12:27 ` Carlos López [this message]
2024-05-26 23:13 ` 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=ff240b23-4143-4171-8dcc-1fdbf1802e8c@suse.de \
--to=clopez@suse.de \
--cc=alan.maguire@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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
all inboxes | Powered by JetHome®