Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@xxxxxxxxxxxxx>:
On Tue, 18 Apr 2023 15:53:37 -0700 you wrote:
> Martin reports another case where getsockopt EFAULTs perfectly
> valid callers. Let's fix it and also replace EFAULT with
> pr_info_ratelimited. That should hopefully make this place
> less error prone.
>
> First 2 patches fix the issue with NETLINK_LIST_MEMBERSHIPS and
> test it.
>
> [...]
Here is the summary with links:
- [bpf-next,1/6] bpf: Don't EFAULT for getsockopt with optval=NULL
https://git.kernel.org/bpf/bpf-next/c/00e74ae08638
- [bpf-next,2/6] selftests/bpf: Verify optval=NULL case
https://git.kernel.org/bpf/bpf-next/c/833d67ecdc5f
- [bpf-next,3/6] bpf: Don't EFAULT for {g,s}setsockopt with wrong optlen
(no matching commit)
- [bpf-next,4/6] selftests/bpf: Update EFAULT {g,s}etsockopt selftests
(no matching commit)
- [bpf-next,5/6] selftests/bpf: Correctly handle optlen > 4096
(no matching commit)
- [bpf-next,6/6] bpf: Document EFAULT changes for sockopt
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
