From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
kernel-team@cloudflare.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, john.fastabend@gmail.com,
cong.wang@bytedance.com
Subject: Re: [PATCH bpf] bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets
Date: Fri, 29 Sep 2023 15:20:25 +0000 [thread overview]
Message-ID: <169600082536.24887.16932433184368539961.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230920102055.42662-1-jakub@cloudflare.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 20 Sep 2023 12:20:55 +0200 you wrote:
> With a SOCKMAP/SOCKHASH map and an sk_msg program user can steer messages
> sent from one TCP socket (s1) to actually egress from another TCP
> socket (s2):
>
> tcp_bpf_sendmsg(s1) // = sk_prot->sendmsg
> tcp_bpf_send_verdict(s1) // __SK_REDIRECT case
> tcp_bpf_sendmsg_redir(s2)
> tcp_bpf_push_locked(s2)
> tcp_bpf_push(s2)
> tcp_rate_check_app_limited(s2) // expects tcp_sock
> tcp_sendmsg_locked(s2) // ditto
>
> [...]
Here is the summary with links:
- [bpf] bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets
https://git.kernel.org/bpf/bpf/c/b80e31baa436
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-09-29 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 10:20 [PATCH bpf] bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets Jakub Sitnicki
2023-09-20 18:19 ` Kui-Feng Lee
2023-09-20 20:59 ` Jakub Sitnicki
2023-09-20 21:11 ` Kui-Feng Lee
2023-09-25 18:27 ` John Fastabend
2023-09-29 15:20 ` 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=169600082536.24887.16932433184368539961.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cong.wang@bytedance.com \
--cc=daniel@iogearbox.net \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@cloudflare.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox