From: Carlos Neira <cneirabustos@gmail.com>
To: netdev@vger.kernel.org
Cc: yhs@fb.com, ebiederm@xmission.com, brouer@redhat.com,
bpf@vger.kernel.org, cneirabustos@gmail.com
Subject: [PATCH v14 0/5] BPF: New helper to obtain namespace data from current task
Date: Thu, 17 Oct 2019 12:00:27 -0300 [thread overview]
Message-ID: <20191017150032.14359-1-cneirabustos@gmail.com> (raw)
Currently bpf_get_current_pid_tgid(), is used to do pid filtering in bcc's
scripts but this helper returns the pid as seen by the root namespace which is
fine when a bcc script is not executed inside a container.
When the process of interest is inside a container, pid filtering will not work
if bpf_get_current_pid_tgid() is used.
This helper addresses this limitation returning the pid as it's seen by the current
namespace where the script is executing.
In the future different pid_ns files may belong to different devices, according to the
discussion between Eric Biederman and Yonghong in 2017 Linux plumbers conference.
To address that situation the helper requires inum and dev_t from /proc/self/ns/pid.
This helper has the same use cases as bpf_get_current_pid_tgid() as it can be
used to do pid filtering even inside a container.
Changes from V13:
- refactored selftests
- refactored ebpf helper
Signed-off-by: Carlos Neira <cneirabustos@gmail.com>
Carlos Neira (5):
fs/nsfs.c: added ns_match
bpf: added new helper bpf_get_ns_current_pid_tgid
tools: Added bpf_get_ns_current_pid_tgid helper
tools/testing/selftests/bpf: Add self-tests for new helper.
bpf_helpers_doc.py: Add struct bpf_pidns_info to known types
fs/nsfs.c | 8 ++
include/linux/bpf.h | 1 +
include/linux/proc_ns.h | 2 +
include/uapi/linux/bpf.h | 20 +++-
kernel/bpf/core.c | 1 +
kernel/bpf/helpers.c | 45 +++++++++
kernel/trace/bpf_trace.c | 2 +
scripts/bpf_helpers_doc.py | 1 +
tools/include/uapi/linux/bpf.h | 20 +++-
.../bpf/prog_tests/get_ns_current_pid_tgid.c | 96 +++++++++++++++++++
.../bpf/progs/get_ns_current_pid_tgid_kern.c | 53 ++++++++++
11 files changed, 247 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/get_ns_current_pid_tgid.c
create mode 100644 tools/testing/selftests/bpf/progs/get_ns_current_pid_tgid_kern.c
--
2.20.1
next reply other threads:[~2019-10-17 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 15:00 Carlos Neira [this message]
2019-10-17 15:00 ` [PATCH v14 1/5] fs/nsfs.c: added ns_match Carlos Neira
2019-10-18 9:24 ` Simon Horman
2019-10-17 15:00 ` [PATCH v14 2/5] bpf: added new helper bpf_get_ns_current_pid_tgid Carlos Neira
2019-10-18 17:10 ` Yonghong Song
2019-10-17 15:00 ` [PATCH v14 3/5] tools: Added bpf_get_ns_current_pid_tgid helper Carlos Neira
2019-10-18 17:11 ` Yonghong Song
2019-10-17 15:00 ` [PATCH v14 4/5] tools/testing/selftests/bpf: Add self-tests for new helper Carlos Neira
2019-10-18 17:33 ` Yonghong Song
2019-10-21 18:20 ` Andrii Nakryiko
2019-10-21 19:14 ` Carlos Antonio Neira Bustos
2019-10-21 19:18 ` Andrii Nakryiko
2019-10-22 16:50 ` Carlos Antonio Neira Bustos
2019-10-17 15:00 ` [PATCH v14 5/5] bpf_helpers_doc.py: Add struct bpf_pidns_info to known types Carlos Neira
2019-10-18 17:34 ` Yonghong Song
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=20191017150032.14359-1-cneirabustos@gmail.com \
--to=cneirabustos@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=yhs@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;
as well as URLs for NNTP newsgroup(s).