public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxim Mikityanskiy <maximmi@nvidia.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH bpf-next v7 1/6] bpf: Use ipv6_only_sock in bpf_tcp_gen_syncookie
Date: Fri, 29 Apr 2022 12:23:11 +0300	[thread overview]
Message-ID: <0d496e79-afc5-39d6-59be-be4152b9b60b@nvidia.com> (raw)
In-Reply-To: <CAADnVQLw4yz_N3xR59XbSGdCH3ckU-pPWZ93JugomGejfo5hTA@mail.gmail.com>

On 2022-04-29 06:15, Alexei Starovoitov wrote:
> On Thu, Apr 28, 2022 at 8:38 AM Maxim Mikityanskiy <maximmi@nvidia.com> wrote:
>>
>> Instead of querying the sk_ipv6only field directly, use the dedicated
>> ipv6_only_sock helper.
>>
>> Signed-off-by: Maxim Mikityanskiy <maximmi@nvidia.com>
>> Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
>> Acked-by: John Fastabend <john.fastabend@gmail.com>
>> Acked-by: Lorenz Bauer <lmb@cloudflare.com>
>> Acked-by: Petar Penkov <ppenkov@google.com>
>> ---
>>   net/core/filter.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/net/core/filter.c b/net/core/filter.c
>> index 8847316ee20e..207a13db5c80 100644
>> --- a/net/core/filter.c
>> +++ b/net/core/filter.c
>> @@ -7099,7 +7099,7 @@ BPF_CALL_5(bpf_tcp_gen_syncookie, struct sock *, sk, void *, iph, u32, iph_len,
>>           */
>>          switch (((struct iphdr *)iph)->version) {
>>          case 4:
>> -               if (sk->sk_family == AF_INET6 && sk->sk_ipv6only)
>> +               if (sk->sk_family == AF_INET6 && ipv6_only_sock(sk))
>>                          return -EINVAL;
> 
> Please rebase patches before resending.

I'm sorry - it's totally my fault! I didn't fetch before rebasing =/

> Applying: bpf: Use ipv6_only_sock in bpf_tcp_gen_syncookie
> Using index info to reconstruct a base tree...
> M    net/core/filter.c
> Falling back to patching base and 3-way merge...
> Auto-merging net/core/filter.c
> No changes -- Patch already applied.

Someone else has made the same change as my first patch, so I'll drop it.

> Applying: bpf: Fix documentation of th_len in bpf_tcp_{gen,check}_syncookie
> Applying: bpf: Allow helpers to accept pointers with a fixed size
> Applying: bpf: Add helpers to issue and check SYN cookies in XDP
> error: sha1 information is lacking or useless (include/uapi/linux/bpf.h).
> error: could not build fake ancestor
> Patch failed at 0004 bpf: Add helpers to issue and check SYN cookies in XDP
> 
> 
> Also trim your cc. You keep sending to addresses that are bouncing
> (Lorenz's and Petar's).
> 
> Remove their Ack-s too or fix them with correct emails.

As we don't need patch 1 anymore, I will drop it, and we won't have 
these acks anymore. I'll also exclude these people from CC (I only kept 
them because of their acks they gave when their emails still worked).

  reply	other threads:[~2022-04-29  9:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 15:38 [PATCH bpf-next v7 0/6] New BPF helpers to accelerate synproxy Maxim Mikityanskiy
2022-04-28 15:38 ` [PATCH bpf-next v7 1/6] bpf: Use ipv6_only_sock in bpf_tcp_gen_syncookie Maxim Mikityanskiy
2022-04-29  3:15   ` Alexei Starovoitov
2022-04-29  9:23     ` Maxim Mikityanskiy [this message]
2022-04-28 15:38 ` [PATCH bpf-next v7 2/6] bpf: Fix documentation of th_len in bpf_tcp_{gen,check}_syncookie Maxim Mikityanskiy
2022-04-28 15:38 ` [PATCH bpf-next v7 3/6] bpf: Allow helpers to accept pointers with a fixed size Maxim Mikityanskiy
2022-04-28 15:38 ` [PATCH bpf-next v7 4/6] bpf: Add helpers to issue and check SYN cookies in XDP Maxim Mikityanskiy
2022-04-28 15:38 ` [PATCH bpf-next v7 5/6] bpf: Add selftests for raw syncookie helpers Maxim Mikityanskiy
2022-04-28 15:38 ` [PATCH bpf-next v7 6/6] bpf: Allow the new syncookie helpers to work with SKBs Maxim Mikityanskiy

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=0d496e79-afc5-39d6-59be-be4152b9b60b@nvidia.com \
    --to=maximmi@nvidia.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --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