Re: [PATCH bpf-next 1/2] libbpf: handle nulled-out program in struct_ops correctly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello:

This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@xxxxxxxxxx>:

On Sat, 27 Apr 2024 20:09:53 -0700 you wrote:
> If struct_ops has one of program callbacks set declaratively and host
> kernel is old and doesn't support this callback, libbpf will allow to
> load such struct_ops as long as that callback was explicitly nulled-out
> (presumably through skeleton). This is all working correctly, except we
> won't reset corresponding program slot to NULL before bailing out, which
> will lead to libbpf not detecting that BPF program has to be not
> auto-loaded. Fix this by unconditionally resetting corresponding program
> slot to NULL.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] libbpf: handle nulled-out program in struct_ops correctly
    https://git.kernel.org/bpf/bpf-next/c/f973fccd43d3
  - [bpf-next,2/2] selftests/bpf: validate nulled-out struct_ops program is handled properly
    https://git.kernel.org/bpf/bpf-next/c/1bba3b3d373d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html






[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux