From: Stanislav Fomichev <sdf@google.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, ast@kernel.org, daniel@iogearbox.net,
Stanislav Fomichev <sdf@google.com>
Subject: [PATCH bpf-next 0/5] add bpf cgroup hooks that trigger on socket close
Date: Thu, 17 Jan 2019 16:41:01 -0800 [thread overview]
Message-ID: <20190118004106.163825-1-sdf@google.com> (raw)
Currently, we have BPF_CGROUP_INET_SOCK_CREATE hook that triggers on
socket creation and there is no way to know when the socket is being
closed. Add new set of hooks BPF_CGROUP_INET{4,6}_SOCK_RELEASE
that trigger when the socket is closed.
Initial intended usecase is to cleanup statistics after POST{4,6}_BIND.
Hooks have read-only access to all fields of struct bpf_sock.
First patch adds hooks, the rest of the patches add uapi and tests to make
sure these hooks work.
Stanislav Fomichev (5):
bpf: add BPF_CGROUP_INET{4,6}_SOCK_RELEASE hooks
tools: bpf: support BPF_CGROUP_INET{4,6}_SOCK_RELEASE in
libbpf/bpftool
selftests/bpf: add BPF_CGROUP_INET{4,6}_SOCK_RELEASE to
test_section_names.c
selftests/bpf: add BPF_CGROUP_INET{4,6}_SOCK_RELEASE to test_sock.c
selftests/bpf: add BPF_CGROUP_INET{4,6}_SOCK_RELEASE to
test_sock_addr.c
include/linux/bpf-cgroup.h | 6 +
include/net/inet_common.h | 1 +
include/uapi/linux/bpf.h | 2 +
kernel/bpf/syscall.c | 8 ++
net/core/filter.c | 7 +
net/ipv4/af_inet.c | 13 +-
net/ipv6/af_inet6.c | 5 +-
tools/bpf/bpftool/cgroup.c | 2 +
tools/include/uapi/linux/bpf.h | 2 +
tools/lib/bpf/libbpf.c | 4 +
.../selftests/bpf/test_section_names.c | 10 ++
tools/testing/selftests/bpf/test_sock.c | 119 ++++++++++++++++
tools/testing/selftests/bpf/test_sock_addr.c | 131 +++++++++++++++++-
13 files changed, 307 insertions(+), 3 deletions(-)
--
2.20.1.321.g9e740568ce-goog
next reply other threads:[~2019-01-18 0:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 0:41 Stanislav Fomichev [this message]
2019-01-18 0:41 ` [PATCH bpf-next 1/5] bpf: add BPF_CGROUP_INET{4,6}_SOCK_RELEASE hooks Stanislav Fomichev
2019-01-18 2:22 ` Andrey Ignatov
2019-01-18 6:30 ` kbuild test robot
2019-01-18 7:23 ` kbuild test robot
2019-01-18 0:41 ` [PATCH bpf-next 2/5] tools: bpf: support BPF_CGROUP_INET{4,6}_SOCK_RELEASE in libbpf/bpftool Stanislav Fomichev
2019-01-18 0:41 ` [PATCH bpf-next 3/5] selftests/bpf: add BPF_CGROUP_INET{4,6}_SOCK_RELEASE to test_section_names.c Stanislav Fomichev
2019-01-18 0:41 ` [PATCH bpf-next 4/5] selftests/bpf: add BPF_CGROUP_INET{4,6}_SOCK_RELEASE to test_sock.c Stanislav Fomichev
2019-01-18 0:41 ` [PATCH bpf-next 5/5] selftests/bpf: add BPF_CGROUP_INET{4,6}_SOCK_RELEASE to test_sock_addr.c Stanislav Fomichev
2019-01-18 2:45 ` Andrey Ignatov
2019-01-18 1:02 ` [PATCH bpf-next 0/5] add bpf cgroup hooks that trigger on socket close Eric Dumazet
2019-01-18 1:58 ` Stanislav Fomichev
2019-01-18 2:36 ` Andrey Ignatov
2019-01-18 16:50 ` Stanislav Fomichev
2019-01-18 22:39 ` Andrey Ignatov
2019-01-22 17:00 ` Stanislav Fomichev
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=20190118004106.163825-1-sdf@google.com \
--to=sdf@google.com \
--cc=ast@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;
as well as URLs for NNTP newsgroup(s).