From: sdf@google•com
To: Martin KaFai Lau <kafai@fb•com>
Cc: bpf@vger•kernel.org, Alexei Starovoitov <ast@kernel•org>,
Daniel Borkmann <daniel@iogearbox•net>,
kernel-team@fb•com, netdev@vger•kernel.org
Subject: Re: [PATCH bpf-next 0/2] Do not limit cb_flags when creating child sk from listen sk
Date: Fri, 2 Oct 2020 09:03:06 -0700 [thread overview]
Message-ID: <20201002160306.GB1856340@google.com> (raw)
In-Reply-To: <20201002013442.2541568-1-kafai@fb.com>
On 10/01, Martin KaFai Lau wrote:
> This set fixes an issue that the bpf_skops_init_child() unnecessarily
> limited the child sk from inheriting all bpf_sock_ops_cb_flags
> of the listen sk. It also adds a test to check that.
Thank you, that fixed it for me!
Tested-by: Stanislav Fomichev <sdf@google•com>
prev parent reply other threads:[~2020-10-02 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 1:34 [PATCH bpf-next 0/2] Do not limit cb_flags when creating child sk from listen sk Martin KaFai Lau
2020-10-02 1:34 ` [PATCH bpf-next 1/2] bpf: tcp: " Martin KaFai Lau
2020-10-02 1:34 ` [PATCH bpf-next 2/2] bpf: selftest: Ensure the child sk inherited all bpf_sock_ops_cb_flags Martin KaFai Lau
2020-10-02 16:03 ` sdf [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=20201002160306.GB1856340@google.com \
--to=sdf@google$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=kafai@fb$(echo .)com \
--cc=kernel-team@fb$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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