From: sdf@google.com
To: Xin Liu <liuxin350@huawei.com>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, yanan@huawei.com,
wuchangye@huawei.com, xiesongyang@huawei.com,
kongweibin2@huawei.com, zhangmingyi5@huawei.com
Subject: Re: [PATCH] libbpf: fix crash when input null program point in USDT API
Date: Mon, 19 Dec 2022 10:50:18 -0800 [thread overview]
Message-ID: <Y6CyatoFytXToO/g@google.com> (raw)
In-Reply-To: <20221219064613.2932-1-liuxin350@huawei.com>
On 12/19, Xin Liu wrote:
> The API functions bpf_program__attach_perf_event_opts and
> bpf_program_attach_usdt can be invoked by users. However, when the
> input prog parameter is null, the API uses name and obj without
> check. This will cause program to crash directly.
Why do we care about these only? We have a lot of functions invoked
by the users which don't check the arguments. Can the caller ensure
the prog is valid/consistent before calling these?
> Signed-off-by: Xin Liu <liuxin350@huawei.com>
> ---
> tools/lib/bpf/libbpf.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> index 2a82f49ce16f..0d21de4f7d5c 100644
> --- a/tools/lib/bpf/libbpf.c
> +++ b/tools/lib/bpf/libbpf.c
> @@ -9764,6 +9764,11 @@ struct bpf_link
> *bpf_program__attach_perf_event_opts(const struct bpf_program *p
> if (!OPTS_VALID(opts, bpf_perf_event_opts))
> return libbpf_err_ptr(-EINVAL);
> + if (!prog || !prog->name) {
> + pr_warn("prog: invalid prog\n");
> + return libbpf_err_ptr(-EINVAL);
> + }
> +
> if (pfd < 0) {
> pr_warn("prog '%s': invalid perf event FD %d\n",
> prog->name, pfd);
> @@ -10967,7 +10972,7 @@ struct bpf_link *bpf_program__attach_usdt(const
> struct bpf_program *prog,
> const struct bpf_usdt_opts *opts)
> {
> char resolved_path[512];
> - struct bpf_object *obj = prog->obj;
> + struct bpf_object *obj;
> struct bpf_link *link;
> __u64 usdt_cookie;
> int err;
> @@ -10975,6 +10980,11 @@ struct bpf_link *bpf_program__attach_usdt(const
> struct bpf_program *prog,
> if (!OPTS_VALID(opts, bpf_uprobe_opts))
> return libbpf_err_ptr(-EINVAL);
> + if (!prog || !prog->name || !prog->obj) {
> + pr_warn("prog: invalid prog\n");
> + return libbpf_err_ptr(-EINVAL);
> + }
> +
> if (bpf_program__fd(prog) < 0) {
> pr_warn("prog '%s': can't attach BPF program w/o FD (did you load
> it?)\n",
> prog->name);
> @@ -10997,6 +11007,7 @@ struct bpf_link *bpf_program__attach_usdt(const
> struct bpf_program *prog,
> /* USDT manager is instantiated lazily on first USDT attach. It will
> * be destroyed together with BPF object in bpf_object__close().
> */
> + obj = prog->obj;
> if (IS_ERR(obj->usdt_man))
> return libbpf_ptr(obj->usdt_man);
> if (!obj->usdt_man) {
> --
> 2.33.0
next prev parent reply other threads:[~2022-12-19 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 6:46 [PATCH] libbpf: fix crash when input null program point in USDT API Xin Liu
2022-12-19 18:50 ` sdf [this message]
2022-12-20 1:56 ` Xin Liu
2022-12-20 23:53 ` Andrii Nakryiko
2022-12-23 1:09 ` Xin Liu
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=Y6CyatoFytXToO/g@google.com \
--to=sdf@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kongweibin2@huawei.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuxin350@huawei.com \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
--cc=wuchangye@huawei.com \
--cc=xiesongyang@huawei.com \
--cc=yanan@huawei.com \
--cc=yhs@fb.com \
--cc=zhangmingyi5@huawei.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