From: Carlos Antonio Neira Bustos <cneirabustos@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Network Development <netdev@vger.kernel.org>,
Yonghong Song <yhs@fb.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jesper Dangaard Brouer <brouer@redhat.com>,
bpf <bpf@vger.kernel.org>, Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH v16 0/5] BPF: New helper to obtain namespace data from current task
Date: Fri, 10 Jan 2020 10:27:11 -0300 [thread overview]
Message-ID: <20200110132711.GA1772684@frodo.byteswizards.com> (raw)
In-Reply-To: <CAADnVQKQLTLvND=249aR2tYm-SxcJ9BbVi-SQUwuoOpt01knZw@mail.gmail.com>
On Thu, Jan 09, 2020 at 05:46:29PM -0800, Alexei Starovoitov wrote:
> On Wed, Dec 18, 2019 at 9:38 AM Carlos Neira <cneirabustos@gmail.com> wrote:
> >
> > 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.
>
> I think the set looks like fine. Please respin against bpf-next
> carrying over Yonghong's ack and I'll apply it.
> Please squash patch 2 and 3 together.
> Updates to tools/uapi/bpf.h don't need to be separated anymore.
> Patch 5 can be squashed into them as well.
> Could you also improve selftest from patch 4 to test new helper
> both inside and outside of some container?
> With unshare(CLONE_NEWPID) or something.
> Do you have corresponding bcc change to show how it's going to be used?
Thanks Alexei,
I'll squash patches 2, 3, 5 together and improve the new helper test, regarding bcc
changes, I also need to work on that as the one I created a while ago now
is not valid https://github.com/iovisor/bcc/pull/1901/commits/a81b4352173cb82922d4d4bb965a39f781fd7693
Bests
prev parent reply other threads:[~2020-01-10 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 17:38 [PATCH v16 0/5] BPF: New helper to obtain namespace data from current task Carlos Neira
2019-12-18 17:38 ` [PATCH v16 1/5] fs/nsfs.c: added ns_match Carlos Neira
2019-12-19 18:45 ` Yonghong Song
2019-12-18 17:38 ` [PATCH v16 2/5] bpf: added new helper bpf_get_ns_current_pid_tgid Carlos Neira
2019-12-19 18:31 ` Yonghong Song
2019-12-18 17:38 ` [PATCH v16 3/5] tools: Added bpf_get_ns_current_pid_tgid helper Carlos Neira
2019-12-19 18:31 ` Yonghong Song
2019-12-18 17:38 ` [PATCH v16 4/5] tools/testing/selftests/bpf: Add self-tests for new helper bpf_get_ns_current_pid_tgid Carlos Neira
2019-12-19 18:40 ` Yonghong Song
2019-12-18 17:38 ` [PATCH v16 5/5] bpf_helpers_doc.py: Add struct bpf_pidns_info to known types Carlos Neira
2019-12-19 18:43 ` Yonghong Song
2020-01-10 1:46 ` [PATCH v16 0/5] BPF: New helper to obtain namespace data from current task Alexei Starovoitov
2020-01-10 13:27 ` Carlos Antonio Neira Bustos [this message]
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=20200110132711.GA1772684@frodo.byteswizards.com \
--to=cneirabustos@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--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).