[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230718100345.c4ba0e4c1e52e9b028697f98@kernel.org>
Date: Tue, 18 Jul 2023 10:03:45 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
linux-trace-kernel@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>,
bpf <bpf@...r.kernel.org>, Sven Schnelle <svens@...ux.ibm.com>,
Alexei Starovoitov <ast@...nel.org>
Subject: Re: [PATCH v2 2/9] bpf/btf: tracing: Move finding func-proto API
and getting func-param API to BTF
On Mon, 17 Jul 2023 16:51:29 -0700
Alexei Starovoitov <alexei.starovoitov@...il.com> wrote:
> On Mon, Jul 17, 2023 at 4:46 PM Masami Hiramatsu <mhiramat@...nel.org> wrote:
> >
> > >
> > > > + * Return NULL if not found, or return -EINVAL if parameter is invalid.
> > > > + */
> > > > +const struct btf_type *btf_find_func_proto(struct btf *btf, const char *func_name)
> > > > +{
> > > > + const struct btf_type *t;
> > > > + s32 id;
> > > > +
> > > > + if (!btf || !func_name)
> > > > + return ERR_PTR(-EINVAL);
>
> Please remove these checks.
> We don't do defensive programming in the BPF subsystem.
> Don't pass NULL pointers to such functions.
OK, we will trust API user to pass a non-NULL parameters.
Thank you!
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists