From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, gregory.detal@gmail.com,
marcelo.leitner@gmail.com, lucien.xin@gmail.com,
vyasevich@gmail.com, nhorman@tuxdriver.com,
wangweidong1@huawei.com, daniel@iogearbox.net,
vyasevic@redhat.com, allison.henderson@oracle.com,
sowmini.varadhan@oracle.com, viro@zeniv.linux.org.uk,
joel.granados@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sctp@vger.kernel.org,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
stable@vger.kernel.org,
syzbot+e364f774c6f57f2c86d1@syzkaller.appspotmail.com
Subject: Re: [PATCH net 0/9] net: sysctl: avoid using current->nsproxy
Date: Thu, 09 Jan 2025 17:00:48 +0000 [thread overview]
Message-ID: <173644204876.1449021.3388211513784045754.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250108-net-sysctl-current-nsproxy-v1-0-5df34b2083e8@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 08 Jan 2025 16:34:28 +0100 you wrote:
> As pointed out by Al Viro and Eric Dumazet in [1], using the 'net'
> structure via 'current' is not recommended for different reasons:
>
> - Inconsistency: getting info from the reader's/writer's netns vs only
> from the opener's netns as it is usually done. This could cause
> unexpected issues when other operations are done on the wrong netns.
>
> [...]
Here is the summary with links:
- [net,1/9] mptcp: sysctl: avail sched: remove write access
https://git.kernel.org/netdev/net/c/771ec78dc8b4
- [net,2/9] mptcp: sysctl: sched: avoid using current->nsproxy
https://git.kernel.org/netdev/net/c/d38e26e36206
- [net,3/9] mptcp: sysctl: blackhole timeout: avoid using current->nsproxy
https://git.kernel.org/netdev/net/c/92cf7a51bdae
- [net,4/9] sctp: sysctl: cookie_hmac_alg: avoid using current->nsproxy
https://git.kernel.org/netdev/net/c/ea62dd138391
- [net,5/9] sctp: sysctl: rto_min/max: avoid using current->nsproxy
https://git.kernel.org/netdev/net/c/9fc17b76fc70
- [net,6/9] sctp: sysctl: auth_enable: avoid using current->nsproxy
https://git.kernel.org/netdev/net/c/15649fd5415e
- [net,7/9] sctp: sysctl: udp_port: avoid using current->nsproxy
https://git.kernel.org/netdev/net/c/c10377bbc197
- [net,8/9] sctp: sysctl: plpmtud_probe_interval: avoid using current->nsproxy
https://git.kernel.org/netdev/net/c/6259d2484d0c
- [net,9/9] rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy
https://git.kernel.org/netdev/net/c/7f5611cbc487
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:[~2025-01-09 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 15:34 [PATCH net 0/9] net: sysctl: avoid using current->nsproxy Matthieu Baerts (NGI0)
2025-01-08 15:34 ` [PATCH net 1/9] mptcp: sysctl: avail sched: remove write access Matthieu Baerts (NGI0)
2025-01-08 16:25 ` Eric Dumazet
2025-01-08 15:34 ` [PATCH net 2/9] mptcp: sysctl: sched: avoid using current->nsproxy Matthieu Baerts (NGI0)
2025-01-08 15:34 ` [PATCH net 3/9] mptcp: sysctl: blackhole timeout: " Matthieu Baerts (NGI0)
2025-01-08 15:34 ` [PATCH net 4/9] sctp: sysctl: cookie_hmac_alg: " Matthieu Baerts (NGI0)
2025-01-08 15:34 ` [PATCH net 5/9] sctp: sysctl: rto_min/max: " Matthieu Baerts (NGI0)
2025-01-08 15:34 ` [PATCH net 6/9] sctp: sysctl: auth_enable: " Matthieu Baerts (NGI0)
2025-01-08 15:34 ` [PATCH net 7/9] sctp: sysctl: udp_port: " Matthieu Baerts (NGI0)
2025-01-08 15:34 ` [PATCH net 8/9] sctp: sysctl: plpmtud_probe_interval: " Matthieu Baerts (NGI0)
2025-01-08 15:34 ` [PATCH net 9/9] rds: sysctl: rds_tcp_{rcv,snd}buf: " Matthieu Baerts (NGI0)
2025-01-09 17:00 ` 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=173644204876.1449021.3388211513784045754.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=gregory.detal@gmail.com \
--cc=horms@kernel.org \
--cc=joel.granados@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=sowmini.varadhan@oracle.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+e364f774c6f57f2c86d1@syzkaller.appspotmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=vyasevic@redhat.com \
--cc=vyasevich@gmail.com \
--cc=wangweidong1@huawei.com \
/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