Re: [PATCH net-next v3 0/4] net: move .getsockopt away from __user buffers
From: patchwork-bot+netdevbpf
Date: Mon Apr 13 2026 - 18:34:20 EST
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@xxxxxxxxxx>:
On Wed, 08 Apr 2026 03:30:28 -0700 you wrote:
> Currently, the .getsockopt callback requires __user pointers:
>
> int (*getsockopt)(struct socket *sock, int level,
> int optname, char __user *optval, int __user *optlen);
>
> This prevents kernel callers (io_uring, BPF) from using getsockopt on
> levels other than SOL_SOCKET, since they pass kernel pointers.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] net: add getsockopt_iter callback to proto_ops
https://git.kernel.org/netdev/net-next/c/67fab22a7adc
- [net-next,v3,2/4] net: call getsockopt_iter if available
https://git.kernel.org/netdev/net-next/c/5bd0dec150f5
- [net-next,v3,3/4] af_packet: convert to getsockopt_iter
https://git.kernel.org/netdev/net-next/c/9c99d6270569
- [net-next,v3,4/4] can: raw: convert to getsockopt_iter
https://git.kernel.org/netdev/net-next/c/5b75e7d67695
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html