From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Juri Lelli <juri.lelli@redhat.com>, bpf <bpf@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Artem Savkov <asavkov@redhat.com>,
"Jose E. Marchesi" <jose.marchesi@oracle.com>
Subject: Re: NULL pointer deref when running BPF monitor program (6.11.0-rc1)
Date: Fri, 16 Aug 2024 15:30:40 -0400 [thread overview]
Message-ID: <20240816153040.14d36c77@rorschach.local.home> (raw)
In-Reply-To: <Zr-ho0ncAk__sZiX@krava>
On Fri, 16 Aug 2024 20:59:47 +0200
Jiri Olsa <olsajiri@gmail.com> wrote:
> so far the only working solution I have is adding '__nullable' suffix
> to argument name:
>
> diff --git a/include/trace/events/sched.h b/include/trace/events/sched.h
> index 9ea4c404bd4e..fc46f0b42741 100644
> --- a/include/trace/events/sched.h
> +++ b/include/trace/events/sched.h
> @@ -559,9 +559,9 @@ DEFINE_EVENT(sched_stat_runtime, sched_stat_runtime,
> */
> TRACE_EVENT(sched_pi_setprio,
>
> - TP_PROTO(struct task_struct *tsk, struct task_struct *pi_task),
> + TP_PROTO(struct task_struct *tsk, struct task_struct *pi_task__nullable),
>
> - TP_ARGS(tsk, pi_task),
> + TP_ARGS(tsk, pi_task__nullable),
>
> TP_STRUCT__entry(
> __array( char, comm, TASK_COMM_LEN )
> @@ -574,8 +574,8 @@ TRACE_EVENT(sched_pi_setprio,
> memcpy(__entry->comm, tsk->comm, TASK_COMM_LEN);
> __entry->pid = tsk->pid;
> __entry->oldprio = tsk->prio;
> - __entry->newprio = pi_task ?
> - min(tsk->normal_prio, pi_task->prio) :
> + __entry->newprio = pi_task__nullable ?
> + min(tsk->normal_prio, pi_task__nullable->prio) :
> tsk->normal_prio;
> /* XXX SCHED_DEADLINE bits missing */
> ),
>
>
> now I'm trying to make work something like:
>
> diff --git a/include/trace/events/sched.h b/include/trace/events/sched.h
> index 9ea4c404bd4e..4e4aae2d5700 100644
> --- a/include/trace/events/sched.h
> +++ b/include/trace/events/sched.h
> @@ -559,9 +559,9 @@ DEFINE_EVENT(sched_stat_runtime, sched_stat_runtime,
> */
> TRACE_EVENT(sched_pi_setprio,
>
> - TP_PROTO(struct task_struct *tsk, struct task_struct *pi_task),
> + TP_PROTO(struct task_struct *tsk, struct task_struct *__nullable(pi_task)),
>
> - TP_ARGS(tsk, pi_task),
> + TP_ARGS(tsk, __nullable(pi_task)),
>
> TP_STRUCT__entry(
> __array( char, comm, TASK_COMM_LEN )
Hmm, that's really ugly though. Both versions.
Now when Alexei said:
> > > > > We cannot make all tracepoint pointers to be PTR_TRUSTED | PTR_MAYBE_NULL
> > > > > by default, since it will break a bunch of progs.
> > > > > Instead we can annotate this tracepoint arg as __nullable and
> > > > > teach the verifier to recognize such special arguments of tracepoints.
I'm not familiar with the verifier, so I don't know how the above is
implemented, and why it would break a bunch of progs.
If you had a macro around the parameter:
TP_PROTO(struct task_struct *tsk, struct task_struct *__nullable(pi_task)),
Could having that go through another macro pass in trace_events.h work?
That is, could we associate the trace event with "nullable" parameters
that could be stored someplace else for you?
-- Steve
next prev parent reply other threads:[~2024-08-16 19:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 9:20 NULL pointer deref when running BPF monitor program (6.11.0-rc1) Juri Lelli
2024-08-05 16:49 ` Jiri Olsa
2024-08-05 17:00 ` Alexei Starovoitov
2024-08-06 7:08 ` Juri Lelli
2024-08-06 13:17 ` Jiri Olsa
2024-08-06 13:24 ` Jiri Olsa
2024-08-06 18:44 ` Alexei Starovoitov
2024-08-08 10:46 ` Jiri Olsa
2024-08-08 15:43 ` Alexei Starovoitov
2024-08-15 11:48 ` Jiri Olsa
2024-08-15 12:37 ` Alexei Starovoitov
2024-08-16 14:10 ` Steven Rostedt
2024-08-16 18:59 ` Jiri Olsa
2024-08-16 19:30 ` Steven Rostedt [this message]
2024-08-19 11:47 ` Jiri Olsa
2024-08-19 14:05 ` Jiri Olsa
2024-08-19 15:37 ` Steven Rostedt
2024-08-20 10:17 ` Jiri Olsa
2024-08-20 15:05 ` Steven Rostedt
2024-10-02 16:30 ` Jiri Olsa
2024-10-09 20:41 ` Jiri Olsa
2024-10-10 0:33 ` Josh Poimboeuf
2024-10-10 0:56 ` Steven Rostedt
2024-10-10 0:57 ` Steven Rostedt
2024-10-10 3:17 ` Josh Poimboeuf
2024-10-10 9:00 ` Jiri Olsa
2024-10-10 13:49 ` 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=20240816153040.14d36c77@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=asavkov@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=jose.marchesi@oracle.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olsajiri@gmail.com \
/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