[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168021123724.16527.2802678466803935794.git-patchwork-notify@kernel.org>
Date: Thu, 30 Mar 2023 21:20:37 +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,
yhs@...com, 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,
memxor@...il.com
Subject: Re: [PATCH bpf-next 1/2] bpf: Handle PTR_MAYBE_NULL case in PTR_TO_BTF_ID
helper call arg
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Thu, 30 Mar 2023 09:52:02 -0500 you wrote:
> When validating a helper function argument, we use check_reg_type() to
> ensure that the register containing the argument is of the correct type.
> When the register's base type is PTR_TO_BTF_ID, there is some
> supplemental logic where we do extra checks for various combinations of
> PTR_TO_BTF_ID type modifiers. For example, for PTR_TO_BTF_ID,
> PTR_TO_BTF_ID | PTR_TRUSTED, and PTR_TO_BTF_ID | MEM_RCU, we call
> map_kptr_match_type() for bpf_kptr_xchg() calls, and
> btf_struct_ids_match() for other helper calls.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Handle PTR_MAYBE_NULL case in PTR_TO_BTF_ID helper call arg
https://git.kernel.org/bpf/bpf-next/c/e4c2acab95a5
- [bpf-next,2/2] selftests/bpf: Add testcases for ptr_*_or_null_ in bpf_kptr_xchg
https://git.kernel.org/bpf/bpf-next/c/67efbd57bc6e
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