From: Burn Alting <burn.alting@iinet.net.au>
To: Paul Moore <paul@paul-moore.com>
Cc: Linux-Audit Mailing List <linux-audit@redhat.com>
Subject: Re: BPF audit logs
Date: Thu, 22 Dec 2022 10:49:57 +1100 [thread overview]
Message-ID: <fcbc45f170fa7b45fd441f597e4b9203e17ae2a7.camel@iinet.net.au> (raw)
In-Reply-To: <CAHC9VhSL4NYNXuc629b=CzDzLqg67T-mjp3hiiet_JfzPYC1ug@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 636 bytes --]
On Wed, 2022-12-21 at 18:40 -0500, Paul Moore wrote:
> On Wed, Dec 21, 2022 at 4:03 PM Burn Alting <burn@swtf.dyndns.org> wrote:
> > As Steve suggests, it would have value to provide more information (name, tag,
> > uid) and I don't know if it's possiblebut relate it to the bpf syscall's file
> > descriptor for the map created or program loaded (the exit value).
>
> I'm primarily focused on the bogus ID during load, as that is anobvious regression
> that needs to be addressed as soon as possible.For various backport/support
> reasons, I don't want to combine the bugfix with the feature enhancement of adding
> new fields.
Ack.
[-- Attachment #1.2: Type: text/html, Size: 1117 bytes --]
[-- Attachment #2: Type: text/plain, Size: 107 bytes --]
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2022-12-21 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 22:36 BPF audit logs Burn Alting
2022-12-20 23:16 ` Steve Grubb
2022-12-21 0:01 ` Burn Alting
2022-12-21 14:44 ` Paul Moore
2022-12-21 14:54 ` Paul Moore
2022-12-21 21:02 ` Burn Alting
2022-12-21 23:40 ` Paul Moore
2022-12-21 23:49 ` Burn Alting [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=fcbc45f170fa7b45fd441f597e4b9203e17ae2a7.camel@iinet.net.au \
--to=burn.alting@iinet.net.au \
--cc=burn@swtf.dyndns.org \
--cc=linux-audit@redhat.com \
--cc=paul@paul-moore.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 read-only IMAP folder(s) and NNTP newsgroup(s).