From: patchwork-bot+netdevbpf@kernel.org
To: Jordan Rife <jrife@google.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, willemdebruijn.kernel@gmail.com,
netdev@vger.kernel.org, dborkman@kernel.org, horms@verge.net.au,
pablo@netfilter.org, kadlec@netfilter.org, fw@strlen.de,
santosh.shilimkar@oracle.com, ast@kernel.org, rdna@fb.com,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
coreteam@netfilter.org, netfilter-devel@vger.kernel.org,
ja@ssi.bg, lvs-devel@vger.kernel.org, kafai@fb.com,
daniel@iogearbox.net, daan.j.demeyer@gmail.com
Subject: Re: [PATCH net v6 0/3] Insulate Kernel Space From SOCK_ADDR Hooks
Date: Sun, 01 Oct 2023 18:40:25 +0000 [thread overview]
Message-ID: <169618562530.20334.3438760815048190740.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230926200505.2804266-1-jrife@google.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 26 Sep 2023 15:05:02 -0500 you wrote:
> ==OVERVIEW==
>
> The sock_sendmsg(), kernel_connect(), and kernel_bind() functions
> provide kernel space equivalents to the sendmsg(), connect(), and bind()
> system calls.
>
> When used in conjunction with BPF SOCK_ADDR hooks that rewrite the send,
> connect, or bind address, callers may observe that the address passed to
> the call is modified. This is a problem not just in theory, but in
> practice, with uninsulated calls to kernel_connect() causing issues with
> broken NFS and CIFS mounts.
>
> [...]
Here is the summary with links:
- [net,v6,1/3] net: replace calls to sock->ops->connect() with kernel_connect()
https://git.kernel.org/netdev/net/c/26297b4ce1ce
- [net,v6,2/3] net: prevent rewrite of msg_name and msg_namelen in sock_sendmsg()
(no matching commit)
- [net,v6,3/3] net: prevent address rewrite in kernel_bind()
https://git.kernel.org/netdev/net/c/c889a99a21bf
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:[~2023-10-01 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 20:05 [PATCH net v6 0/3] Insulate Kernel Space From SOCK_ADDR Hooks Jordan Rife
2023-09-26 20:05 ` [PATCH net v6 1/3] net: replace calls to sock->ops->connect() with kernel_connect() Jordan Rife
2023-09-26 20:05 ` [PATCH net v6 2/3] net: prevent rewrite of msg_name and msg_namelen in sock_sendmsg() Jordan Rife
2023-09-26 20:05 ` [PATCH net v6 3/3] net: prevent address rewrite in kernel_bind() Jordan Rife
2023-10-01 18:40 ` 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=169618562530.20334.3438760815048190740.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=coreteam@netfilter.org \
--cc=daan.j.demeyer@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dborkman@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=jrife@google.com \
--cc=kadlec@netfilter.org \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=rdna@fb.com \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=willemdebruijn.kernel@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).