From: Sargun Dhillon <sargun@sargun.me>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: netdev@vger.kernel.org, daniel@iogearbox.net
Subject: Re: [net-next 0/2] BPF, kprobes: Add current_in_cgroup helper
Date: Sat, 6 Aug 2016 21:56:06 -0700 [thread overview]
Message-ID: <20160807045605.GA10067@ircssh.c.rugged-nimbus-611.internal> (raw)
In-Reply-To: <20160807043203.GA77894@ast-mbp>
On Sat, Aug 06, 2016 at 09:32:05PM -0700, Alexei Starovoitov wrote:
> On Sat, Aug 06, 2016 at 09:06:53PM -0700, Sargun Dhillon wrote:
> > This patchset includes a helper and an example to determine whether the kprobe
> > is currently executing in the context of a specific cgroup based on a cgroup
> > bpf map / array.
>
> description is too short to understand how this new helper is going to be used.
> depending on kprobe current is not always valid.
Anything not in in_interrupt() should have a current, right?
> what are you trying to achieve?
This is primarily to help troubleshoot containers (Docker, and now systemd). A
lot of the time we want to determine what's going on in a given container
(opening files, connecting to systems, etc...). There's not really a great way
to restrict to containers except by manually walking datastructures to check for
the right cgroup. This seems like a better alternative.
> This looks like an alternative to lsm patches submitted earlier?
No. But I would like to use this helper in the LSM patches I'm working on. For
now, with those patches, and this helper, I can create a map sized 1, and add
the cgroup I care about to it. Given I can add as many bpf programs to an LSM
hook I want, I can use this mechanism to "attach BPF programs to cgroups" --
I put that in quotes because you're not really attaching it to a cgroup,
but just burning some instructions on checking it.
In my mind it seems better than making cgroup-attachment a first-class part
of the checmate work since I still want to make globally available hooks
possible.
> btw net-next is closed and no new features accepted at the moment.
Sorry, I didn't realize that. I'd still love to get feedback.
>
next prev parent reply other threads:[~2016-08-07 4:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 4:06 [net-next 0/2] BPF, kprobes: Add current_in_cgroup helper Sargun Dhillon
2016-08-07 4:32 ` Alexei Starovoitov
2016-08-07 4:56 ` Sargun Dhillon [this message]
2016-08-08 0:52 ` Alexei Starovoitov
2016-08-08 3:08 ` Sargun Dhillon
2016-08-08 3:52 ` Alexei Starovoitov
2016-08-08 9:27 ` Daniel Borkmann
2016-08-08 18:09 ` Sargun Dhillon
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=20160807045605.GA10067@ircssh.c.rugged-nimbus-611.internal \
--to=sargun@sargun.me \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.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