From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: Linux-Audit Mailing List <linux-audit@redhat.com>
Subject: Re: [PATCH v4 3/3] audit: add OPENAT2 record to list how
Date: Thu, 21 Oct 2021 15:00:24 -0400 [thread overview]
Message-ID: <8841192.CDJkKcVGEf@x2> (raw)
In-Reply-To: <20211004182718.GE3977594@madcap2.tricolour.ca>
On Monday, October 4, 2021 2:27:18 PM EDT Richard Guy Briggs wrote:
> > As a heads-up, I had to change the AUDIT_OPENAT2 value to 1337 as the
> > 1336 value is already in use by AUDIT_URINGOP. It wasn't caught
> > during my initial build test as the LSM/audit io_uring patches are in
> > selinux/next and not audit/next, it wasn't until the kernel-secnext
> > build was merging everything for its test run that the collision
> > occurred. I'll be updating the audit/next tree with the new value
> > shortly.
>
> I was expecting a conflict, so thanks for the heads up, Paul.
>
> Steve: This affects the audit userspace support for this patchset
> previously published 2021-05-19 as:
> https://github.com/rgbriggs/audit-userspace/tree/ghau-openat2
>
> The update is here:
> https://github.com/rgbriggs/audit-userspace/tree/ghau-openat2.v2
>
> And a PR has been created:
> https://github.com/linux-audit/audit-userspace/pull/219
The user space piece is now merged.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2021-10-21 19:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 20:00 [PATCH v4 0/3] audit: add support for openat2 Richard Guy Briggs
2021-05-19 20:00 ` [PATCH v4 1/3] audit: replace magic audit syscall class numbers with macros Richard Guy Briggs
2021-05-20 7:50 ` Christian Brauner
2021-08-05 22:01 ` Paul Moore
2021-09-30 20:38 ` Paul Moore
2021-10-01 19:53 ` Richard Guy Briggs
2021-10-01 20:34 ` Paul Moore
2021-10-04 15:34 ` Paul Moore
2021-05-19 20:00 ` [PATCH v4 2/3] audit: add support for the openat2 syscall Richard Guy Briggs
2021-05-20 7:58 ` Christian Brauner
2021-05-24 23:04 ` Paul Moore
2022-02-09 3:44 ` Jeff Mahoney
2022-02-09 15:57 ` Paul Moore
2022-02-09 21:18 ` Paul Moore
2022-02-09 22:13 ` Richard Guy Briggs
2022-02-09 22:31 ` Paul Moore
2022-02-09 21:40 ` Richard Guy Briggs
2022-02-09 22:29 ` Paul Moore
2021-05-19 20:00 ` [PATCH v4 3/3] audit: add OPENAT2 record to list how Richard Guy Briggs
2021-05-20 8:03 ` Christian Brauner
2021-05-24 23:08 ` Paul Moore
2021-05-25 15:00 ` Richard Guy Briggs
2021-10-04 16:08 ` Paul Moore
2021-10-04 18:27 ` Richard Guy Briggs
2021-10-21 19:00 ` Steve Grubb [this message]
2021-10-21 19:44 ` Richard Guy Briggs
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=8841192.CDJkKcVGEf@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=rgb@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