From: patchwork-bot+netdevbpf@kernel.org
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: shuah@kernel.org, andrii@kernel.org, ast@kernel.org,
daniel@iogearbox.net, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
linux-kselftest@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix segfault in bpf_tcp_ca
Date: Mon, 13 Dec 2021 21:40:09 +0000 [thread overview]
Message-ID: <163943160943.5662.15434893142890658156.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211213183058.346066-1-jean-philippe@linaro.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 13 Dec 2021 18:30:59 +0000 you wrote:
> Since commit ad9a7f96445b ("libbpf: Improve logging around BPF program
> loading"), libbpf_debug_print() gets an additional prog_name parameter
> but doesn't pass it to printf(). Since the format string now expects two
> arguments, printf() may read uninitialized data and segfault. Pass
> prog_name through.
>
> Fixes: ad9a7f96445b ("libbpf: Improve logging around BPF program loading")
> Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Fix segfault in bpf_tcp_ca
https://git.kernel.org/bpf/bpf-next/c/acd143eefb82
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-12-13 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 18:30 [PATCH bpf-next] selftests/bpf: Fix segfault in bpf_tcp_ca Jean-Philippe Brucker
2021-12-13 21:40 ` patchwork-bot+netdevbpf [this message]
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=163943160943.5662.15434893142890658156.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jean-philippe@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.