From: Martin KaFai Lau <martin.lau@linux.dev>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: Kuniyuki Iwashima <kuni1840@gmail.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
David Ahern <dsahern@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>
Subject: Re: [PATCH v1 bpf-next 10/11] bpf: tcp: Make WS, SACK, ECN configurable from BPF SYN Cookie.
Date: Tue, 17 Oct 2023 18:08:34 -0700 [thread overview]
Message-ID: <66f72518-f9d6-f19b-60a6-eff0f30c2590@linux.dev> (raw)
In-Reply-To: <20231013220433.70792-11-kuniyu@amazon.com>
On 10/13/23 3:04 PM, Kuniyuki Iwashima wrote:
> This patch allows BPF_SOCK_OPS_CHECK_SYNCOOKIE_CB hook to enable WScale,
> SACK, and ECN by passing corresponding flags to bpf_sock_ops.replylong[1].
>
> The same flags are passed to BPF_SOCK_OPS_GEN_SYNCOOKIE_CB hook as
> bpf_sock_ops.args[1] so that the BPF prog need not parse the TCP header to
> check if WScale, SACK, ECN, and TS are available in SYN.
>
> Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
> ---
> include/uapi/linux/bpf.h | 18 ++++++++++++++++++
> net/ipv4/syncookies.c | 20 ++++++++++++++++++++
> net/ipv4/tcp_input.c | 11 +++++++++++
> tools/include/uapi/linux/bpf.h | 18 ++++++++++++++++++
> 4 files changed, 67 insertions(+)
>
> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
> index 24f673d88c0d..cdae4dd5d797 100644
> --- a/include/uapi/linux/bpf.h
> +++ b/include/uapi/linux/bpf.h
> @@ -6869,6 +6869,7 @@ enum {
> * option.
> *
> * args[0]: MSS
> + * args[1]: BPF_SYNCOOKIE_XXX
> *
> * replylong[0]: ISN
> * replylong[1]: TS
> @@ -6883,6 +6884,7 @@ enum {
> * args[1]: TS
> *
> * replylong[0]: MSS
> + * replylong[1]: BPF_SYNCOOKIE_XXX
> */
> };
>
> @@ -6970,6 +6972,22 @@ enum {
> */
> };
>
> +/* arg[1] value for BPF_SOCK_OPS_GEN_SYNCOOKIE_CB and
> + * replylong[1] for BPF_SOCK_OPS_CHECK_SYNCOOKIE_CB.
> + *
> + * MSB LSB
> + * | 31 ... | 6 | 5 | 4 | 3 2 1 0 |
> + * | ... | TS | ECN | SACK | WScale |
> + */
> +enum {
> + /* 0xf is invalid thus means that SYN did not have WScale. */
> + BPF_SYNCOOKIE_WSCALE_MASK = (1 << 4) - 1,
> + BPF_SYNCOOKIE_SACK = (1 << 4),
> + BPF_SYNCOOKIE_ECN = (1 << 5),
> + /* Only available for BPF_SOCK_OPS_GEN_SYNCOOKIE_CB to check if SYN has TS */
> + BPF_SYNCOOKIE_TS = (1 << 6),
> +};
This details should not be exposed to uapi (more below).
> +
> struct bpf_perf_event_value {
> __u64 counter;
> __u64 enabled;
> diff --git a/net/ipv4/syncookies.c b/net/ipv4/syncookies.c
> index ff979cc314da..22353a9af52d 100644
> --- a/net/ipv4/syncookies.c
> +++ b/net/ipv4/syncookies.c
> @@ -286,6 +286,7 @@ int bpf_skops_cookie_check(struct sock *sk, struct request_sock *req, struct sk_
> {
> struct bpf_sock_ops_kern sock_ops;
> struct net *net = sock_net(sk);
> + u32 options;
>
> if (tcp_opt->saw_tstamp) {
> if (!READ_ONCE(net->ipv4.sysctl_tcp_timestamps))
> @@ -309,6 +310,25 @@ int bpf_skops_cookie_check(struct sock *sk, struct request_sock *req, struct sk_
> if (!sock_ops.replylong[0])
> goto err;
>
> + options = sock_ops.replylong[1];
> +
> + if ((options & BPF_SYNCOOKIE_WSCALE_MASK) != BPF_SYNCOOKIE_WSCALE_MASK) {
> + if (!READ_ONCE(net->ipv4.sysctl_tcp_window_scaling))
> + goto err;
> +
> + tcp_opt->wscale_ok = 1;
> + tcp_opt->snd_wscale = options & BPF_SYNCOOKIE_WSCALE_MASK;
> + }
> +
> + if (options & BPF_SYNCOOKIE_SACK) {
> + if (!READ_ONCE(net->ipv4.sysctl_tcp_sack))
> + goto err;
> +
> + tcp_opt->sack_ok = 1;
> + }
> +
> + inet_rsk(req)->ecn_ok = options & BPF_SYNCOOKIE_ECN;
> +
> __NET_INC_STATS(sock_net(sk), LINUX_MIB_SYNCOOKIESRECV);
>
> return sock_ops.replylong[0];
> diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
> index feb44bff29ef..483e2f36afe5 100644
> --- a/net/ipv4/tcp_input.c
> +++ b/net/ipv4/tcp_input.c
> @@ -6970,14 +6970,25 @@ EXPORT_SYMBOL_GPL(tcp_get_syncookie_mss);
> static int bpf_skops_cookie_init_sequence(struct sock *sk, struct request_sock *req,
> struct sk_buff *skb, __u32 *isn)
> {
> + struct inet_request_sock *ireq = inet_rsk(req);
> struct bpf_sock_ops_kern sock_ops;
> + u32 options;
> int ret;
>
> + options = ireq->wscale_ok ? ireq->snd_wscale : BPF_SYNCOOKIE_WSCALE_MASK;
> + if (ireq->sack_ok)
> + options |= BPF_SYNCOOKIE_SACK;
> + if (ireq->ecn_ok)
> + options |= BPF_SYNCOOKIE_ECN;
> + if (ireq->tstamp_ok)
> + options |= BPF_SYNCOOKIE_TS;
No need to set "options" (which becomes args[1]). sock_ops.sk is available to
the bpf prog. The bpf prog can directly read it. The recent AF_UNIX bpf support
could be a reference on how the bpf_cast_to_kern_ctx() and bpf_rdonly_cast() are
used.
https://lore.kernel.org/bpf/20231011185113.140426-10-daan.j.demeyer@gmail.com/
> +
> memset(&sock_ops, 0, offsetof(struct bpf_sock_ops_kern, temp));
>
> sock_ops.op = BPF_SOCK_OPS_GEN_SYNCOOKIE_CB;
> sock_ops.sk = req_to_sk(req);
> sock_ops.args[0] = req->mss;
> + sock_ops.args[1] = options;
>
> bpf_skops_init_skb(&sock_ops, skb, tcp_hdrlen(skb));
>
> diff --git a/tools/include/uapi/linux/bpf.h b/tools/include/uapi/linux/bpf.h
> index 24f673d88c0d..cdae4dd5d797 100644
> --- a/tools/include/uapi/linux/bpf.h
> +++ b/tools/include/uapi/linux/bpf.h
> @@ -6869,6 +6869,7 @@ enum {
> * option.
> *
> * args[0]: MSS
> + * args[1]: BPF_SYNCOOKIE_XXX
> *
> * replylong[0]: ISN
> * replylong[1]: TS
> @@ -6883,6 +6884,7 @@ enum {
> * args[1]: TS
> *
> * replylong[0]: MSS
> + * replylong[1]: BPF_SYNCOOKIE_XXX
> */
> };
>
> @@ -6970,6 +6972,22 @@ enum {
> */
> };
>
> +/* arg[1] value for BPF_SOCK_OPS_GEN_SYNCOOKIE_CB and
> + * replylong[1] for BPF_SOCK_OPS_CHECK_SYNCOOKIE_CB.
> + *
> + * MSB LSB
> + * | 31 ... | 6 | 5 | 4 | 3 2 1 0 |
> + * | ... | TS | ECN | SACK | WScale |
> + */
> +enum {
> + /* 0xf is invalid thus means that SYN did not have WScale. */
> + BPF_SYNCOOKIE_WSCALE_MASK = (1 << 4) - 1,
> + BPF_SYNCOOKIE_SACK = (1 << 4),
> + BPF_SYNCOOKIE_ECN = (1 << 5),
> + /* Only available for BPF_SOCK_OPS_GEN_SYNCOOKIE_CB to check if SYN has TS */
> + BPF_SYNCOOKIE_TS = (1 << 6),
> +};
> +
> struct bpf_perf_event_value {
> __u64 counter;
> __u64 enabled;
next prev parent reply other threads:[~2023-10-18 1:08 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 22:04 [PATCH v1 bpf-next 00/11] bpf: tcp: Add SYN Cookie generation/validation SOCK_OPS hooks Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 01/11] tcp: Clean up reverse xmas tree in cookie_v[46]_check() Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 02/11] tcp: Cache sock_net(sk) " Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 03/11] tcp: Clean up goto labels " Kuniyuki Iwashima
2023-10-17 0:00 ` Kui-Feng Lee
2023-10-17 0:30 ` Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 04/11] tcp: Don't initialise tp->tsoffset in tcp_get_cookie_sock() Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 05/11] bpf: tcp: Add SYN Cookie generation SOCK_OPS hook Kuniyuki Iwashima
2023-10-18 0:54 ` Martin KaFai Lau
2023-10-18 17:00 ` Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 06/11] bpf: tcp: Add SYN Cookie validation " Kuniyuki Iwashima
2023-10-16 20:38 ` Stanislav Fomichev
2023-10-16 22:02 ` Kuniyuki Iwashima
2023-10-17 16:52 ` Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 07/11] bpf: Make bpf_sock_ops.replylong[1] writable Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 08/11] bpf: tcp: Make TS available for SYN Cookie storage Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 09/11] tcp: Split cookie_ecn_ok() Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 10/11] bpf: tcp: Make WS, SACK, ECN configurable from BPF SYN Cookie Kuniyuki Iwashima
2023-10-18 1:08 ` Martin KaFai Lau [this message]
2023-10-18 17:02 ` Kuniyuki Iwashima
2023-10-13 22:04 ` [PATCH v1 bpf-next 11/11] selftest: bpf: Test BPF_SOCK_OPS_(GEN|CHECK)_SYNCOOKIE_CB Kuniyuki Iwashima
2023-10-17 5:50 ` Martin KaFai Lau
2023-10-17 16:29 ` Kuniyuki Iwashima
2023-10-16 13:05 ` [PATCH v1 bpf-next 00/11] bpf: tcp: Add SYN Cookie generation/validation SOCK_OPS hooks Daniel Borkmann
2023-10-16 16:11 ` Kuniyuki Iwashima
2023-10-16 14:19 ` Willem de Bruijn
2023-10-16 16:46 ` Kuniyuki Iwashima
2023-10-16 18:41 ` Willem de Bruijn
2023-10-17 5:53 ` Martin KaFai Lau
2023-10-17 16:48 ` Kuniyuki Iwashima
2023-10-18 6:19 ` Martin KaFai Lau
2023-10-18 8:02 ` Eric Dumazet
2023-10-18 17:20 ` Kuniyuki Iwashima
2023-10-18 21:47 ` Kui-Feng Lee
2023-10-18 22:31 ` Kuniyuki Iwashima
2023-10-19 7:25 ` Martin KaFai Lau
2023-10-19 18:01 ` Kuniyuki Iwashima
2023-10-20 19:59 ` Martin KaFai Lau
2023-10-20 23:10 ` Kuniyuki Iwashima
2023-10-21 6:48 ` Kuniyuki Iwashima
2023-10-23 21:35 ` Martin KaFai Lau
2023-10-24 0:37 ` Kui-Feng Lee
2023-10-24 1:22 ` Kuniyuki Iwashima
2023-10-24 17:55 ` Kui-Feng Lee
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=66f72518-f9d6-f19b-60a6-eff0f30c2590@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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 NNTP newsgroup(s).