mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Doruk Tan Ozturk <doruk@0sec.ai>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrew+netdev@lunn.ch, fmancera@suse.de,
	sd@queasysnail.net, linville@tuxdriver.com,
	mschiffer@universe-factory.net, maoyixie.tju@gmail.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] vxlan, geneve: require CAP_NET_ADMIN in the device netns for changelink
Date: Thu, 23 Jul 2026 15:20:16 +0000	[thread overview]
Message-ID: <178482001663.2315735.8917962308148940780.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260716203500.70573-1-doruk@0sec.ai>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 16 Jul 2026 22:34:58 +0200 you wrote:
> The recent series "require CAP_NET_ADMIN in the device netns for
> changelink" (8165f7ff57d9..27ccb68e7ccc) added rtnl_dev_link_net_capable()
> and gated the eight IP tunnel drivers (ip_gre, ipip, ip_vti, ip6_tunnel,
> ip6_gre, ip6_vti, sit, xfrm_interface). VXLAN and GENEVE share the exact
> same shape but were not covered: both store the underlay netns sticky at
> newlink (vxlan->net / geneve->net) and their changelink() operates on that
> netns, while the generic RTM_NEWLINK path only checks CAP_NET_ADMIN against
> dev_net(dev). Once such a device is created in or moved to another netns,
> a caller privileged in dev_net(dev) but not in the underlay netns can
> reconfigure the tunnel'"'"'s underlay.
> 
> [...]

Here is the summary with links:
  - [net,v2,1/2] vxlan: require CAP_NET_ADMIN in the device netns for changelink
    https://git.kernel.org/netdev/net/c/3a61bd9637f3
  - [net,v2,2/2] geneve: require CAP_NET_ADMIN in the device netns for changelink
    https://git.kernel.org/netdev/net/c/8efb8f8bbb35

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



      parent reply	other threads:[~2026-07-23 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 20:34 Doruk Tan Ozturk
2026-07-16 20:34 ` [PATCH net v2 1/2] vxlan: " Doruk Tan Ozturk
2026-07-16 21:37   ` Fernando Fernandez Mancera
2026-07-16 20:35 ` [PATCH net v2 2/2] geneve: " Doruk Tan Ozturk
2026-07-16 21:37   ` Fernando Fernandez Mancera
2026-07-23 15:20 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178482001663.2315735.8917962308148940780.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=doruk@0sec.ai \
    --cc=edumazet@google.com \
    --cc=fmancera@suse.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=maoyixie.tju@gmail.com \
    --cc=mschiffer@universe-factory.net \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®