BPF List
 help / color / mirror / Atom feed
From: Kui-Feng Lee <sinquersw@gmail.com>
To: Martin KaFai Lau <martin.lau@linux.dev>, Kui-Feng Lee <kuifeng@meta.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, song@kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH bpf-next v3 2/2] selftests/bpf: Calls bpf_setsockopt() on a ktls enabled socket.
Date: Thu, 26 Jan 2023 10:12:17 -0800	[thread overview]
Message-ID: <14f48f2a-918c-6545-537c-a724b19b4137@gmail.com> (raw)
In-Reply-To: <638f080b-ee7d-2cd6-07e1-dbbc2dcded0f@linux.dev>


On 1/25/23 15:17, Martin KaFai Lau wrote:
> On 1/25/23 12:16 PM, Kui-Feng Lee wrote:
>> +    close(fd);
>> +    /* At this point, the cfd socket is at the CLOSE_WAIT state
>> +     * and still run TLS protocol.  The test for
>> +     * BPF_TCP_CLOSE_WAIT should be run at this point.
>> +     */
>> +    char buf[1];
>
> This checkpatch warning is reasonable:
>
> https://patchwork.kernel.org/project/netdevbpf/patch/20230125201608.908230-3-kuifeng@meta.com/ 
>
>
> WARNING: Missing a blank line after declarations
> #88: FILE: tools/testing/selftests/bpf/prog_tests/setget_sockopt.c:138:
> +    char buf[1];
> +    ret = read(cfd, buf, 1);
>
> I fixed it up and take this chance to move it to the beginning of the 
> function. Applied. Thanks.


Thank you for fixing that and reviewing!


>
>
>> +    ret = read(cfd, buf, 1);
>> +    ASSERT_EQ(ret, 0, "read");
>> +    close(cfd);
>

  reply	other threads:[~2023-01-26 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 20:16 [PATCH bpf-next v3 0/2] Enable bpf_setsockopt() on ktls enabled sockets Kui-Feng Lee
2023-01-25 20:16 ` [PATCH bpf-next v3 1/2] bpf: Check the protocol of a sock to agree the calls to bpf_setsockopt() Kui-Feng Lee
2023-01-25 20:16 ` [PATCH bpf-next v3 2/2] selftests/bpf: Calls bpf_setsockopt() on a ktls enabled socket Kui-Feng Lee
2023-01-25 23:17   ` Martin KaFai Lau
2023-01-26 18:12     ` Kui-Feng Lee [this message]
2023-01-25 23:20 ` [PATCH bpf-next v3 0/2] Enable bpf_setsockopt() on ktls enabled sockets patchwork-bot+netdevbpf

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=14f48f2a-918c-6545-537c-a724b19b4137@gmail.com \
    --to=sinquersw@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=kernel-team@meta.com \
    --cc=kuifeng@meta.com \
    --cc=martin.lau@linux.dev \
    --cc=song@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