Re: [RFC] audit support for BPF notification
On Fri, Aug 09, 2019 at 01:45:21PM -0400, Steve Grubb wrote:
Hello,
On Friday, August 9, 2019 10:18:31 AM EDT Jiri Olsa wrote:
> I posted initial change that allows auditd to log BPF program
> load/unload events, it's in here:
> https://github.com/linux-audit/audit-userspace/pull/104
Thanks for the patch...but we probably should have talked a bit more before
undertaking this effort. We normally do not audit from user space what happens
in the kernel. Doing this can be racy and it keeps auditd from doing the one
job it has - which is to grab events and record them to disk and send them
out the realtime interface.
> We tried to push pure AUDIT interface for BPF program notification,
> but it was denied, the discussion is in here:
> https://marc.info/?t=153866123200003&r=1&w=2
Hmm. The email I remember was here:
https://www.redhat.com/archives/linux-audit/2018-October/msg00053.html
and was only 2 emails long with no answer to my question. :-)
oops, sry about that, your question was:
I'm not sure exactly what the issue is. You can audit for
specific syscall
and argument. So, if you want to see loads, then you can make a rule like:
-a always,exit -F arch=b64 -S bpf -F a0=5
The problem with above for us is that we also:
- need to log also other properties of the BPF program,
which are not visible from BPF syscall arguments, like
its ID, JIT status or license info
- need to see BPF program UNLOAD, which is not done
via syscall, so those would be unvisible at all
> The outcome of the discussion was to use perf event interface
> for BPF notification and use it in some deamon.. audit was our
> first choice.
>
> thoughts?
I'd like to understand what the basic problem is that needs to be solved.
we need a way for administrators to see the history of loaded BPF
programs, to help investigating issues related to BPF.. and the
only BPF interface for this data is through perf ring buffer
jirka