From: Daniel Borkmann <daniel@iogearbox.net>
To: Andrey Ignatov <rdna@fb.com>, netdev@vger.kernel.org
Cc: ast@kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Test sys_connect BPF hooks with TFO
Date: Wed, 27 Jun 2018 11:28:32 +0200 [thread overview]
Message-ID: <2a83e656-db3e-d7ed-2a18-e6cacbe5cfa6@iogearbox.net> (raw)
In-Reply-To: <20180626212241.3298872-1-rdna@fb.com>
On 06/26/2018 11:22 PM, Andrey Ignatov wrote:
> TCP Fast Open is triggered by sys_sendmsg with MSG_FASTOPEN flag for
> SOCK_STREAM socket.
>
> Even though it's sys_sendmsg, it eventually calls __inet_stream_connect
> the same way sys_connect does for TCP. __inet_stream_connect, in turn,
> already has BPF hooks for sys_connect.
>
> That means TFO is already covered by BPF_CGROUP_INET{4,6}_CONNECT and
> the only missing piece is selftest. The patch adds selftest for TFO.
>
> Signed-off-by: Andrey Ignatov <rdna@fb.com>
Applied to bpf-next, thanks Andrey!
prev parent reply other threads:[~2018-06-27 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 21:22 [PATCH bpf-next] selftests/bpf: Test sys_connect BPF hooks with TFO Andrey Ignatov
2018-06-27 9:28 ` Daniel Borkmann [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=2a83e656-db3e-d7ed-2a18-e6cacbe5cfa6@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=rdna@fb.com \
/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