public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin KaFai Lau <martin.lau@linux.dev>
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: Jiayuan Chen <jiayuan.chen@shopee.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Eduard Zingerman <eddyz87@gmail.com>, 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@fomichev.me>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	bpf@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf v1 2/2] selftests/bpf: Add protocol check test for bpf_sk_assign_tcp_reqsk()
Date: Wed, 25 Mar 2026 23:33:20 -0700	[thread overview]
Message-ID: <12cc6b53-d801-4e77-83d6-b2a4655ec1b8@linux.dev> (raw)
In-Reply-To: <4c27a461-2714-4c27-8604-dedd506a09aa@linux.dev>

On 3/25/26 8:24 PM, Jiayuan Chen wrote:
> 
> On 3/25/26 5:59 AM, Martin KaFai Lau wrote:
>> On 3/23/26 3:54 AM, Jiayuan Chen wrote:
>>> +void test_tcp_custom_syncookie_protocol_check(void)
>>> +{
>>> +    struct test_tcp_custom_syncookie *skel;
>>> +    struct sockaddr_in tcp_addr, udp_addr;
>>> +    socklen_t addr_len = sizeof(tcp_addr);
>>> +    int tcp_server = -1, udp_client = -1;
>>> +    char buf[32] = "test";
>>> +    int ret;
>>> +
>>> +    if (setup_netns())
>>> +        return;
>>> +
>>> +    skel = test_tcp_custom_syncookie__open_and_load();
>>> +    if (!ASSERT_OK_PTR(skel, "open_and_load"))
>>> +        return;
>>>   +    /* Create a TCP listener so the BPF can find a LISTEN socket */
>>> +    tcp_server = start_server(AF_INET, SOCK_STREAM, "127.0.0.1", 0, 0);
>>> +    if (!ASSERT_NEQ(tcp_server, -1, "start tcp_server"))
>>> +        goto destroy_skel;
>>> +
>>> +    ret = getsockname(tcp_server, (struct sockaddr *)&tcp_addr, 
>>> &addr_len);
>>> +    if (!ASSERT_OK(ret, "getsockname"))
>>> +        goto close_tcp;
>>> +
>>> +    skel->bss->tcp_listener_port = ntohs(tcp_addr.sin_port);
>>> +    skel->bss->udp_test_port = 9999;
>>> +
>>> +    ret = bpf_program__fd(skel->progs.tcp_custom_syncookie_badproto);
>>> +    if (setup_tc(ret))
>>> +        goto close_tcp;
>>> +
>>> +    udp_client = socket(AF_INET, SOCK_DGRAM, 0);
>>> +    if (!ASSERT_NEQ(udp_client, -1, "udp socket"))
>>> +        goto cleanup_tc;
>>> +
>>> +    memset(&udp_addr, 0, sizeof(udp_addr));
>>> +    udp_addr.sin_family = AF_INET;
>>> +    udp_addr.sin_addr.s_addr = htonl(INADDR_LOOPBACK);
>>> +    udp_addr.sin_port = htons(9999);
>>> +
>>> +    ret = sendto(udp_client, buf, sizeof(buf), 0,
>>> +             (struct sockaddr *)&udp_addr, sizeof(udp_addr));
>>> +    ASSERT_EQ(ret, sizeof(buf), "sendto udp");
>>> +
>>> +    /* Wait for TC ingress BPF to process the skb. */
>>> +    kern_sync_rcu();
>>
>> hmm... is it guaranteed to work? Regardless, it checks the error 
>> returned from bpf_sk_assign_tcp_reqsk(). Maybe bpf_prog_test_run is 
>> simpler?
>>
>> pw-bot: cr
>>
>>> +
>>>
> I looked into using bpf_prog_test_run, but it won't work here
> because bpf_sk_assign_tcp_reqsk() requires the skb to come from TC ingress
> — it checks skb_at_tc_ingress() internally and returns -EINVAL otherwise.

Thanks for trying.

> 
> For the synchronization concern, instead of kern_sync_rcu(), I now create
> a UDP server bound to the target port and recv() the packet after sendto().
> Since the BPF program returns TC_ACT_OK, the packet passes through TC 
> ingress
> and arrives at the UDP socket. The recv() naturally blocks until the BPF 
> program
> has finished processing, so no timing tricks are needed.
> 

sgtm.

      reply	other threads:[~2026-03-26  6:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 10:54 [PATCH bpf v1 0/2] bpf: tcp: Fix null-ptr-deref in arbitrary SYN Cookie Jiayuan Chen
2026-03-23 10:54 ` [PATCH bpf v1 1/2] bpf: tcp: Reject non-TCP skb in bpf_sk_assign_tcp_reqsk() Jiayuan Chen
2026-03-24 21:37   ` Martin KaFai Lau
2026-03-26  0:04   ` Kuniyuki Iwashima
2026-03-26  1:54     ` Jiayuan Chen
2026-03-23 10:54 ` [PATCH bpf v1 2/2] selftests/bpf: Add protocol check test for bpf_sk_assign_tcp_reqsk() Jiayuan Chen
2026-03-24 21:59   ` Martin KaFai Lau
2026-03-25  2:03     ` Jiayuan Chen
2026-03-26  3:24     ` Jiayuan Chen
2026-03-26  6:33       ` Martin KaFai Lau [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=12cc6b53-d801-4e77-83d6-b2a4655ec1b8@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=eddyz87@gmail.com \
    --cc=edumazet@google.com \
    --cc=haoluo@google.com \
    --cc=horms@kernel.org \
    --cc=jiayuan.chen@linux.dev \
    --cc=jiayuan.chen@shopee.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --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