[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<169618562530.20334.3438760815048190740.git-patchwork-notify@kernel.org>
Date: Sun, 01 Oct 2023 18:40:25 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jordan Rife <jrife@...gle.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, willemdebruijn.kernel@...il.com, netdev@...r.kernel.org,
dborkman@...nel.org, horms@...ge.net.au, pablo@...filter.org,
kadlec@...filter.org, fw@...len.de, santosh.shilimkar@...cle.com,
ast@...nel.org, rdna@...com, linux-rdma@...r.kernel.org,
rds-devel@....oracle.com, coreteam@...filter.org,
netfilter-devel@...r.kernel.org, ja@....bg, lvs-devel@...r.kernel.org,
kafai@...com, daniel@...earbox.net, daan.j.demeyer@...il.com
Subject: Re: [PATCH net v6 0/3] Insulate Kernel Space From SOCK_ADDR Hooks
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@...emloft.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
Powered by blists - more mailing lists