public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: linux-audit@redhat.com
Cc: "Stanislav Kozina" <skozina@redhat.com>,
	"Yauheni Kaliuta" <yauheni.kaliuta@redhat.com>,
	"Toke Høiland-Jørgensen" <toke@redhat.com>,
	"Jiri Benc" <jbenc@redhat.com>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>,
	"Jesper Dangaard Brouer" <brouer@redhat.com>
Subject: [RFC] audit support for BPF notification
Date: Fri, 9 Aug 2019 16:18:31 +0200	[thread overview]
Message-ID: <20190809141831.GB9377@krava> (raw)

hi,
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

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

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?

thanks,
jirka

             reply	other threads:[~2019-08-09 14:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 14:18 Jiri Olsa [this message]
2019-08-09 17:45 ` [RFC] audit support for BPF notification Steve Grubb
2019-08-12  7:59   ` Jiri Olsa
2019-08-12 13:49     ` Steve Grubb
2019-08-12 14:32       ` Jiri Olsa
2019-08-14  7:33         ` Jiri Olsa
2019-08-20 13:54           ` Jiri Olsa
2019-11-04 13:05             ` Jiri Benc
2019-11-04 13:28               ` Jiri Olsa
2019-11-04 13:41               ` Vladis Dronov
2019-11-04 13:46               ` Vladis Dronov
2019-11-05  0:18               ` Paul Moore

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=20190809141831.GB9377@krava \
    --to=jolsa@redhat.com \
    --cc=acme@redhat.com \
    --cc=brouer@redhat.com \
    --cc=jbenc@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=skozina@redhat.com \
    --cc=toke@redhat.com \
    --cc=yauheni.kaliuta@redhat.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