From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: edumazet@google.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, pabeni@redhat.com,
kuni1840@gmail.com, bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v8 bpf-next 0/6] bpf: tcp: Support arbitrary SYN Cookie at TC.
Date: Wed, 17 Jan 2024 01:50:26 +0000 [thread overview]
Message-ID: <170545622615.24208.8311280954771361156.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240115205514.68364-1-kuniyu@amazon.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Mon, 15 Jan 2024 12:55:08 -0800 you wrote:
> Under SYN Flood, the TCP stack generates SYN Cookie to remain stateless
> for the connection request until a valid ACK is responded to the SYN+ACK.
>
> The cookie contains two kinds of host-specific bits, a timestamp and
> secrets, so only can it be validated by the generator. It means SYN
> Cookie consumes network resources between the client and the server;
> intermediate nodes must remember which nodes to route ACK for the cookie.
>
> [...]
Here is the summary with links:
- [v8,bpf-next,1/6] tcp: Move tcp_ns_to_ts() to tcp.h
https://git.kernel.org/bpf/bpf-next/c/e8a7ea899527
- [v8,bpf-next,2/6] tcp: Move skb_steal_sock() to request_sock.h
https://git.kernel.org/bpf/bpf-next/c/2d1ee30a3b07
- [v8,bpf-next,3/6] bpf: tcp: Handle BPF SYN Cookie in skb_steal_sock().
https://git.kernel.org/bpf/bpf-next/c/5f8b96b9b391
- [v8,bpf-next,4/6] bpf: tcp: Handle BPF SYN Cookie in cookie_v[46]_check().
https://git.kernel.org/bpf/bpf-next/c/311ef79955d3
- [v8,bpf-next,5/6] bpf: tcp: Support arbitrary SYN Cookie.
https://git.kernel.org/bpf/bpf-next/c/b9c3eca5c086
- [v8,bpf-next,6/6] selftest: bpf: Test bpf_sk_assign_tcp_reqsk().
https://git.kernel.org/bpf/bpf-next/c/98af7dca1e0d
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:[~2024-01-17 1:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 20:55 [PATCH v8 bpf-next 0/6] bpf: tcp: Support arbitrary SYN Cookie at TC Kuniyuki Iwashima
2024-01-15 20:55 ` [PATCH v8 bpf-next 1/6] tcp: Move tcp_ns_to_ts() to tcp.h Kuniyuki Iwashima
2024-01-15 20:55 ` [PATCH v8 bpf-next 2/6] tcp: Move skb_steal_sock() to request_sock.h Kuniyuki Iwashima
2024-01-15 20:55 ` [PATCH v8 bpf-next 3/6] bpf: tcp: Handle BPF SYN Cookie in skb_steal_sock() Kuniyuki Iwashima
2024-01-15 20:55 ` [PATCH v8 bpf-next 4/6] bpf: tcp: Handle BPF SYN Cookie in cookie_v[46]_check() Kuniyuki Iwashima
2024-03-15 13:37 ` Eric Dumazet
2024-03-15 19:02 ` Kuniyuki Iwashima
2024-01-15 20:55 ` [PATCH v8 bpf-next 5/6] bpf: tcp: Support arbitrary SYN Cookie Kuniyuki Iwashima
2024-01-17 1:55 ` Martin KaFai Lau
2024-01-15 20:55 ` [PATCH v8 bpf-next 6/6] selftest: bpf: Test bpf_sk_assign_tcp_reqsk() Kuniyuki Iwashima
2024-01-17 1: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=170545622615.24208.8311280954771361156.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=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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