From: David Vernet <void@manifault.com>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next] libbpf: fix memory leak in attach_tp for target-less tracepoint program
Date: Mon, 16 May 2022 12:03:32 -0700 [thread overview]
Message-ID: <20220516190332.5mrld5dranyoeuhd@dev0025.ash9.facebook.com> (raw)
In-Reply-To: <20220516184547.3204674-1-andrii@kernel.org>
On Mon, May 16, 2022 at 11:45:47AM -0700, Andrii Nakryiko wrote:
> Fix sec_name memory leak if user defines target-less SEC("tp").
>
> Fixes: 9af8efc45eb1 ("libbpf: Allow "incomplete" basic tracing SEC() definitions")
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> ---
LGTM
Acked-by: David Vernet <void@manifault.com>
next prev parent reply other threads:[~2022-05-16 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 18:45 [PATCH bpf-next] libbpf: fix memory leak in attach_tp for target-less tracepoint program Andrii Nakryiko
2022-05-16 19:03 ` David Vernet [this message]
2022-05-16 20:50 ` patchwork-bot+netdevbpf
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=20220516190332.5mrld5dranyoeuhd@dev0025.ash9.facebook.com \
--to=void@manifault.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.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