From: Chenbo Feng <chenbofeng.kernel@gmail.com>
To: "David S . Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@fb.com>,
netdev@vger.kernel.org
Cc: Willem de Bruijn <willemb@google.com>,
Lorenzo Colitti <lorenzo@google.com>,
Chenbo Feng <chenbofeng.kernel@gmail.com>
Subject: [PATCH net-next 0/2] net: core: Two Helper function about socket information
Date: Thu, 2 Feb 2017 12:59:48 -0800 [thread overview]
Message-ID: <20170202205950.100334-1-chenbofeng.kernel@gmail.com> (raw)
Introduce two eBpf helper function to get the socket cookie and
socket uid for each packet. The helper function is useful when
the *sk field inside sk_buff is not empty.
Chenbo Feng (2):
Add a helper function to get socket cookie in eBPF
Add a eBPF helper function to retrieve socket uid
include/linux/bpf.h | 2 ++
include/linux/sock_diag.h | 1 +
include/uapi/linux/bpf.h | 16 +++++++++++++++-
net/core/filter.c | 34 ++++++++++++++++++++++++++++++++++
net/core/sock_diag.c | 3 ++-
5 files changed, 54 insertions(+), 2 deletions(-)
--
2.11.0.483.g087da7b7c-goog
next reply other threads:[~2017-02-02 21:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 20:59 Chenbo Feng [this message]
2017-02-02 20:59 ` [PATCH net-next 1/2] Add a helper function to get socket cookie in eBPF Chenbo Feng
2017-02-02 21:23 ` Daniel Borkmann
2017-02-02 20:59 ` [PATCH net-next 2/2] Add a eBPF helper function to retrieve socket uid Chenbo Feng
2017-02-02 21:32 ` Daniel Borkmann
2017-02-03 0:00 ` Lorenzo Colitti
2017-02-03 0:28 ` Daniel Borkmann
2017-02-03 0:31 ` Eric Dumazet
2017-02-03 1:18 ` Lorenzo Colitti
2017-02-03 1:51 ` Eric Dumazet
2017-02-03 8:25 ` Daniel Borkmann
2017-02-06 3:25 ` Lorenzo Colitti
2017-02-03 0:13 ` [PATCH net-next 0/2] net: core: Two Helper function about socket information Alexei Starovoitov
2017-02-03 16:19 ` Lorenzo Colitti
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=20170202205950.100334-1-chenbofeng.kernel@gmail.com \
--to=chenbofeng.kernel@gmail.com \
--cc=ast@fb.com \
--cc=davem@davemloft.net \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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 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.