Re: [PATCH bpf-next v2 1/1] bpf: Include pid, uid and comm in audit output

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 12/15/23 8:53 AM, Yonghong Song wrote:

On 12/15/23 8:38 AM, Dave Tucker wrote:

On 15 Dec 2023, at 15:24, Yonghong Song <yonghong.song@xxxxxxxxx> wrote:


On 12/15/23 6:38 AM, Dave Tucker wrote:
Current output from auditd is as follows:

time->Wed Dec 13 21:39:24 2023
type=BPF msg=audit(1702503564.519:11241): prog-id=439 op=LOAD

This only tells you that a BPF program was loaded, but without
any context. If we include the prog-name, pid, uid and comm we get
output as follows:

time->Wed Dec 13 21:59:59 2023
type=BPF msg=audit(1702504799.156:99528): op=UNLOAD prog-id=50092
prog-name="test" pid=27279 uid=0 comm="new_name"

With pid, uid a system administrator has much better context
over which processes and user loaded which eBPF programs.
comm is useful since processes may be short-lived.

Signed-off-by: Dave Tucker <dave@xxxxxxxxxxxxx>
---

Changes:

v1->v2:
   - Move 'op' to the front of the audit messages
   - Add 'prog-name' to the audit messages
   - Replace deprecated in_irq() with in_hardirq()
   - Remove in_irq() check from bpf_audit_prog since it's always called
     from the task context
Is this true? For condition '(in_hardirq() || irqs_disabled())
', the context will be the task context. But what about nmi and
softirq? The context maynot be the task context, right?
You’re right, my mistake.

Not sure whether this is relevant or not. There was a discussion
in the past about the above condition. See
https://lore.kernel.org/bpf/a93079f2-fcd4-e3ef-3b92-92d443b8e8c6@xxxxxxxx/

The recommended change was

diff --git a/kernel/bpf/syscall.c b/kernel/bpf/syscall.c index a75c54b6f8a3..11df562e481b 100644 --- a/kernel/bpf/syscall.c +++ b/kernel/bpf/syscall.c @@ -2147,7 +2147,7 @@ static void __bpf_prog_put(struct bpf_prog *prog)           struct bpf_prog_aux *aux = prog->aux;

         if (atomic64_dec_and_test(&aux->refcnt)) {
- if (in_irq() || irqs_disabled()) { + if (!in_interrupt()) {                           INIT_WORK(&aux->work, bpf_prog_put_deferred);
                         schedule_work(&aux->work);
                 } else {
include/linux/preempt.h says that in_interrupt is also deprecated.
The condition could also be expressed as in_task().

Okay, I see. in_interrupt() probably means !in_task(). The key issue
is in vfree()
===
void vfree(const void *addr)
{
        struct vm_struct *vm;
        int i;

        if (unlikely(in_interrupt())) {
                vfree_atomic(addr);
                return;
        }

        BUG_ON(in_nmi());
        kmemleak_free(addr);
        might_sleep();
...
===
where if in interrupt, vfree is atomic() and otherwise, it is not.
So if for task context, there are cases in the kernel where
__bpf_prog_put() is inside rcu critical section and this might
cause the problem. But since this is true for a couple of cases,
so it has not been a big issue yet...


If the above change was true, then audit will not be able to
get any meaning task specific information, you might need to
gather such informaiton before hand.
Hmmm. Would storing that information in bpf_prog_aux work?

I think this is more reliable and actually you might get more
useful information, considering once going to kthread, you will
lose task related information.

But for the *current* implementation, you don't need to do that.
You only need to have proper interupt and kthread check in bpf_audit_prog.



- Dave


   - Only populate pid, uid and comm if not in a kthread

  kernel/bpf/syscall.c | 27 ++++++++++++++++++++++-----
  1 file changed, 22 insertions(+), 5 deletions(-)

diff --git a/kernel/bpf/syscall.c b/kernel/bpf/syscall.c
index 06320d9abf33..fbbaf3b8ad48 100644
--- a/kernel/bpf/syscall.c
+++ b/kernel/bpf/syscall.c
@@ -35,6 +35,7 @@
  #include <linux/rcupdate_trace.h>
  #include <linux/memcontrol.h>
  #include <linux/trace_events.h>
+#include <linux/uidgid.h>
    #include <net/netfilter/nf_bpf_link.h>
  #include <net/netkit.h>
@@ -2110,18 +2111,34 @@ static void bpf_audit_prog(const struct bpf_prog *prog, unsigned int op)
  {
   struct audit_context *ctx = NULL;
   struct audit_buffer *ab;
+ const struct cred *cred;
+ char comm[sizeof(current->comm)];
     if (WARN_ON_ONCE(op >= BPF_AUDIT_MAX))
   return;
   if (audit_enabled == AUDIT_OFF)
   return;
- if (!in_irq() && !irqs_disabled())
- ctx = audit_context();
+
+ ctx = audit_context();
   ab = audit_log_start(ctx, GFP_ATOMIC, AUDIT_BPF);
   if (unlikely(!ab))
   return;
- audit_log_format(ab, "prog-id=%u op=%s",
-  prog->aux->id, bpf_audit_str[op]);
+
+ audit_log_format(ab, "op=%s prog-id=%u",
+  bpf_audit_str[op], prog->aux->id);
+ audit_log_format(ab, " prog-name=");
+ audit_log_untrustedstring(ab, prog->aux->name ?: "(none)");
+
+ if (current->mm) {
+ cred = current_cred();
+ audit_log_format(ab, " pid=%u uid=%u",
+  task_pid_nr(current),
+  from_kuid(&init_user_ns, cred->uid));
+ audit_log_format(ab, " comm=");
+ audit_log_untrustedstring(ab, get_task_comm(comm, current));
+ } else {
+ audit_log_format(ab, " pid=? uid=? comm=?");
+ }
   audit_log_end(ab);
  }
  @@ -2212,7 +2229,7 @@ static void __bpf_prog_put(struct bpf_prog *prog)
   struct bpf_prog_aux *aux = prog->aux;
     if (atomic64_dec_and_test(&aux->refcnt)) {
- if (in_irq() || irqs_disabled()) {
+ if (in_hardirq() || irqs_disabled()) {
   INIT_WORK(&aux->work, bpf_prog_put_deferred);
   schedule_work(&aux->work);
   } else {






[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux