From: patchwork-bot+netdevbpf@kernel.org
To: Joanne Koong <joannekoong@fb.com>
Cc: netdev@vger.kernel.org, ebiederm@xmission.com, kuba@kernel.org,
davem@davemloft.net, Kernel-team@fb.com, kafai@fb.com
Subject: Re: [PATCH net-next v2] net: Enable max_dgram_qlen unix sysctl to be configurable by non-init user namespaces
Date: Mon, 13 Dec 2021 12:50:09 +0000 [thread overview]
Message-ID: <163939980999.30215.14697678206955078509.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211210204023.2595573-1-joannekoong@fb.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 10 Dec 2021 12:40:23 -0800 you wrote:
> This patch enables the "/proc/sys/net/unix/max_dgram_qlen" sysctl to be
> exposed to non-init user namespaces. max_dgram_qlen is used as the default
> "sk_max_ack_backlog" value for when a unix socket is created.
>
> Currently, when a networking namespace is initialized, its unix sysctls
> are exposed only if the user namespace that "owns" it is the init user
> namespace. If there is an non-init user namespace that "owns" a networking
> namespace (for example, in the case after we call clone() with both
> CLONE_NEWUSER and CLONE_NEWNET set), the sysctls are hidden from view
> and not configurable.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: Enable max_dgram_qlen unix sysctl to be configurable by non-init user namespaces
https://git.kernel.org/netdev/net-next/c/cec16052d5a7
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:[~2021-12-13 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 20:40 [PATCH net-next v2] net: Enable max_dgram_qlen unix sysctl to be configurable by non-init user namespaces Joanne Koong
2021-12-13 12: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=163939980999.30215.14697678206955078509.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Kernel-team@fb.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=joannekoong@fb.com \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.