[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169688642465.32608.1593187002988701901.git-patchwork-notify@kernel.org>
Date: Mon, 09 Oct 2023 21:20:24 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: David Vernet <void@...ifault.com>
Cc: bpf@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
andrii@...nel.org, martin.lau@...ux.dev, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com,
kpsingh@...nel.org, sdf@...gle.com, haoluo@...gle.com,
jolsa@...nel.org, linux-kernel@...r.kernel.org,
kernel-team@...a.com
Subject: Re: [PATCH bpf-next 1/2] bpf: Fix verifier log for async callback return
values
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Mon, 9 Oct 2023 11:14:13 -0500 you wrote:
> The verifier, as part of check_return_code(), verifies that async
> callbacks such as from e.g. timers, will return 0. It does this by
> correctly checking that R0->var_off is in tnum_const(0), which
> effectively checks that it's in a range of 0. If this condition fails,
> however, it prints an error message which says that the value should
> have been in (0x0; 0x1). This results in possibly confusing output such
> as the following in which an async callback returns 1:
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Fix verifier log for async callback return values
https://git.kernel.org/bpf/bpf/c/829955981c55
- [bpf-next,2/2] bpf/selftests: Add testcase for async callback return value failure
https://git.kernel.org/bpf/bpf/c/57ddeb86b311
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists