On Sun, Feb 9, 2025 at 11:35 PM Feng Yang <yangfeng59949@xxxxxxx> wrote:
>
> From: Feng Yang <yangfeng@xxxxxxxxxx>
>
> This commit 838a10bd2ebf
> ("bpf: Augment raw_tp arguments with PTR_MAYBE_NULL")
> has already resolved the issue, so we can roll back these patches.
> This reverts commit 8aeaed21befc90f27f4fca6dd190850d97d2e9e3.
>
> Signed-off-by: Feng Yang <yangfeng@xxxxxxxxxx>
> ---
> kernel/bpf/btf.c | 3 ---
> kernel/bpf/verifier.c | 36 ++++--------------------------------
> 2 files changed, 4 insertions(+), 35 deletions(-)
>
> diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
> index 9433b6467bbe..e66f98b493d0 100644
> --- a/kernel/bpf/btf.c
> +++ b/kernel/bpf/btf.c
> @@ -6683,9 +6683,6 @@ bool btf_ctx_access(int off, int size, enum bpf_access_type type,
> if (prog_args_trusted(prog))
> info->reg_type |= PTR_TRUSTED;
>
> - if (btf_param_match_suffix(btf, &args[arg], "__nullable"))
> - info->reg_type |= PTR_MAYBE_NULL;
> -
Nack.
This is still useful and necessary.
