Re: [PATCH net-next v2 0/2] net: devmem: allow bind-rx from non-init user namespaces

2026-06-05 Thread patchwork-bot+netdevbpf 
Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski :

On Tue, 02 Jun 2026 18:37:30 -0700 you wrote:
> NETDEV_CMD_BIND_RX is GENL_ADMIN_PERM, which checks CAP_NET_ADMIN
> against init_user_ns. With netkit and netns support for devmem, it is
> now useful to let workloads holding CAP_NET_ADMIN only in their own
> user_ns issue bind-rx for a netns owned by that user_ns.
> 
> The first patch switches the flag to GENL_UNS_ADMIN_PERM so the check
> uses the target netns's owning user_ns. Init remains permitted.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] net: devmem: allow bind-rx from non-init user namespaces
https://git.kernel.org/netdev/net-next/c/e302aa3d00fb
  - [net-next,v2,2/2] selftests: drv-net: add userns devmem RX test
https://git.kernel.org/netdev/net-next/c/78c1930198fc

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

Re: [PATCH net-next v2 0/2] net: devmem: allow bind-rx from non-init user namespaces

2026-06-03 Thread Stanislav Fomichev 
On 06/02, Bobby Eshleman wrote:
> NETDEV_CMD_BIND_RX is GENL_ADMIN_PERM, which checks CAP_NET_ADMIN
> against init_user_ns. With netkit and netns support for devmem, it is
> now useful to let workloads holding CAP_NET_ADMIN only in their own
> user_ns issue bind-rx for a netns owned by that user_ns.
> 
> The first patch switches the flag to GENL_UNS_ADMIN_PERM so the check
> uses the target netns's owning user_ns. Init remains permitted.
> 
> The second patch just adds test cases. They are identical to
> nk_devmem.py tests, but using a non-init userns.
> 
> Signed-off-by: Bobby Eshleman 
> ---
> Changes in v2:
> - some pylint fixes
> - fixed import issue
> - Link to v1: 
> https://lore.kernel.org/all/[email protected]/

Acked-by: Stanislav Fomichev