From: Martin KaFai Lau <kafai@fb.com>
To: <bpf@vger.kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>, <kernel-team@fb.com>,
<netdev@vger.kernel.org>
Subject: [PATCH bpf-next v2 0/4] Provide bpf_sk_storage data in INET_DIAG
Date: Tue, 25 Feb 2020 15:04:02 -0800 [thread overview]
Message-ID: <20200225230402.1974723-1-kafai@fb.com> (raw)
The bpf_prog can store specific info to a sk by using bpf_sk_storage.
In other words, a sk can be extended by a bpf_prog.
This series is to support providing bpf_sk_storage data during inet_diag's
dump. The primary target is the usage like iproute2's "ss".
The first two patches are refactoring works in inet_diag to make
adding bpf_sk_storage support easier. The next two patches do
the actual work.
Please see individual patch for details.
v2:
- Add commit message for u16 to u32 change in min_dump_alloc in Patch 4 (Song)
- Add comment to explain the !skb->len check in __inet_diag_dump in Patch 4.
- Do the map->map_type check earlier in Patch 3 for readability.
Martin KaFai Lau (4):
inet_diag: Refactor inet_sk_diag_fill(), dump(), and dump_one()
inet_diag: Move the INET_DIAG_REQ_BYTECODE nlattr to cb->data
bpf: INET_DIAG support in bpf_sk_storage
bpf: inet_diag: Dump bpf_sk_storages in inet_diag_dump()
include/linux/bpf.h | 1 +
include/linux/inet_diag.h | 27 +--
include/linux/netlink.h | 4 +-
include/net/bpf_sk_storage.h | 27 +++
include/uapi/linux/inet_diag.h | 5 +-
include/uapi/linux/sock_diag.h | 26 +++
kernel/bpf/syscall.c | 15 ++
net/core/bpf_sk_storage.c | 283 +++++++++++++++++++++++++++++-
net/dccp/diag.c | 9 +-
net/ipv4/inet_diag.c | 307 ++++++++++++++++++++-------------
net/ipv4/raw_diag.c | 24 ++-
net/ipv4/tcp_diag.c | 8 +-
net/ipv4/udp_diag.c | 41 +++--
net/sctp/diag.c | 7 +-
14 files changed, 599 insertions(+), 185 deletions(-)
--
2.17.1
next reply other threads:[~2020-02-25 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 23:04 Martin KaFai Lau [this message]
2020-02-25 23:04 ` [PATCH bpf-next v2 1/4] inet_diag: Refactor inet_sk_diag_fill(), dump(), and dump_one() Martin KaFai Lau
2020-02-25 23:04 ` [PATCH bpf-next v2 2/4] inet_diag: Move the INET_DIAG_REQ_BYTECODE nlattr to cb->data Martin KaFai Lau
2020-02-25 23:04 ` [PATCH bpf-next v2 3/4] bpf: INET_DIAG support in bpf_sk_storage Martin KaFai Lau
2020-02-25 23:04 ` [PATCH bpf-next v2 4/4] bpf: inet_diag: Dump bpf_sk_storages in inet_diag_dump() Martin KaFai Lau
2020-02-26 17:21 ` Daniel Borkmann
2020-02-27 1:34 ` Martin KaFai Lau
2020-02-27 6:16 ` Yonghong Song
2020-02-27 23:45 ` Daniel Borkmann
2020-02-28 2:57 ` Alexei Starovoitov
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=20200225230402.1974723-1-kafai@fb.com \
--to=kafai@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.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.