From: Andrey Ignatov <rdna@fb.com>
To: <netdev@vger.kernel.org>
Cc: Andrey Ignatov <rdna@fb.com>, <ast@kernel.org>,
<daniel@iogearbox.net>, <brakmo@fb.com>, <kernel-team@fb.com>
Subject: [PATCH bpf-next 2/6] bpf: Sync bpf.h to tools/
Date: Wed, 11 Jul 2018 17:33:33 -0700 [thread overview]
Message-ID: <cf1ecd7914d07c3ec11ef4a11befe827f1ddbb0c.1531355394.git.rdna@fb.com> (raw)
In-Reply-To: <cover.1531355394.git.rdna@fb.com>
Sync BPF_SOCK_OPS_TCP_LISTEN_CB related UAPI changes to tools/.
Signed-off-by: Andrey Ignatov <rdna@fb.com>
Acked-by: Alexei Starovoitov <ast@kernel.org>
---
tools/include/uapi/linux/bpf.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/include/uapi/linux/bpf.h b/tools/include/uapi/linux/bpf.h
index 59b19b6a40d7..3b0ab93bc94f 100644
--- a/tools/include/uapi/linux/bpf.h
+++ b/tools/include/uapi/linux/bpf.h
@@ -2555,6 +2555,9 @@ enum {
* Arg1: old_state
* Arg2: new_state
*/
+ BPF_SOCK_OPS_TCP_LISTEN_CB, /* Called on listen(2), right after
+ * socket transition to LISTEN state.
+ */
};
/* List of TCP states. There is a build check in net/ipv4/tcp.c to detect
--
2.17.1
next prev parent reply other threads:[~2018-07-12 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 0:33 [PATCH bpf-next 0/6] TCP-BPF callback for listening sockets Andrey Ignatov
2018-07-12 0:33 ` [PATCH bpf-next 1/6] bpf: Add BPF_SOCK_OPS_TCP_LISTEN_CB Andrey Ignatov
2018-07-12 0:33 ` Andrey Ignatov [this message]
2018-07-12 0:33 ` [PATCH bpf-next 3/6] selftests/bpf: Fix const'ness in cgroup_helpers Andrey Ignatov
2018-07-12 0:33 ` [PATCH bpf-next 4/6] selftests/bpf: Switch test_tcpbpf_user to cgroup_helpers Andrey Ignatov
2018-07-12 0:33 ` [PATCH bpf-next 5/6] selftests/bpf: Better verification in test_tcpbpf Andrey Ignatov
2018-07-12 0:33 ` [PATCH bpf-next 6/6] selftests/bpf: Test case for BPF_SOCK_OPS_TCP_LISTEN_CB Andrey Ignatov
2018-07-12 14:59 ` [PATCH bpf-next 0/6] TCP-BPF callback for listening sockets Lawrence Brakmo
2018-07-14 22:18 ` Daniel Borkmann
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=cf1ecd7914d07c3ec11ef4a11befe827f1ddbb0c.1531355394.git.rdna@fb.com \
--to=rdna@fb.com \
--cc=ast@kernel.org \
--cc=brakmo@fb.com \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.