From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Michael_Wei=C3=9F_=3Cmichael=2Eweiss=40aisec=2Efraunhofer=2Ede=3E?=@ci.codeaurora.org
Cc: pabeni@redhat.com, pshelar@ovn.org, davem@davemloft.net,
kuba@kernel.org, joe@cilium.io, azhou@ovn.org,
edumazet@google.com, netdev@vger.kernel.org, dev@openvswitch.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/2] net: openvswitch: metering and conntrack in userns
Date: Tue, 27 Sep 2022 09:50:15 +0000 [thread overview]
Message-ID: <166427221515.2561.12363623872450620942.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220923133820.993725-1-michael.weiss@aisec.fraunhofer.de>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 23 Sep 2022 15:38:18 +0200 you wrote:
> Currently using openvswitch in a non-initial user namespace, e.g., an
> unprivileged container, is possible but without metering and conntrack
> support. This is due to the restriction of the corresponding Netlink
> interfaces to the global CAP_NET_ADMIN.
>
> This simple patches switch from GENL_ADMIN_PERM to GENL_UNS_ADMIN_PERM
> in several cases to allow this also for the unprivileged container
> use case.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/2] net: openvswitch: allow metering in non-initial user namespace
https://git.kernel.org/netdev/net-next/c/803937184717
- [v3,net-next,2/2] net: openvswitch: allow conntrack in non-initial user namespace
https://git.kernel.org/netdev/net-next/c/59cd7377660a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-27 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 13:38 Michael Weiß
2022-09-23 13:38 ` [PATCH v3 net-next 1/2] net: openvswitch: allow metering in non-initial user namespace Michael Weiß
2022-09-23 13:38 ` [PATCH v3 net-next 2/2] net: openvswitch: allow conntrack " Michael Weiß
2022-09-27 9:50 ` 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=166427221515.2561.12363623872450620942.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Michael_Wei=C3=9F_=3Cmichael=2Eweiss=40aisec=2Efraunhofer=2Ede=3E?=@ci.codeaurora.org \
--cc=azhou@ovn.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=joe@cilium.io \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.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®