From: Christian Brauner <christian.brauner@ubuntu.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: Linux-Audit Mailing List <linux-audit@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Paul Moore <paul@paul-moore.com>,
Eric Paris <eparis@parisplace.org>,
Steve Grubb <sgrubb@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Eric Paris <eparis@redhat.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] audit: add support for openat2
Date: Thu, 18 Mar 2021 11:49:32 +0100 [thread overview]
Message-ID: <20210318104932.5225mmecww2fd4zw@wittgenstein> (raw)
In-Reply-To: <cover.1616031035.git.rgb@redhat.com>
On Wed, Mar 17, 2021 at 09:47:16PM -0400, Richard Guy Briggs wrote:
> The openat2(2) syscall was added in v5.6. Add support for openat2 to the
> audit syscall classifier and for recording openat2 parameters that cannot
> be captured in the syscall parameters of the SYSCALL record.
>
> Supporting userspace code can be found in
> https://github.com/rgbriggs/audit-userspace/tree/ghau-openat2
>
> Supporting test case can be found in
> https://github.com/linux-audit/audit-testsuite/pull/103
Seems sensible, thank you.
prev parent reply other threads:[~2021-03-18 10:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 1:47 [PATCH 0/2] audit: add support for openat2 Richard Guy Briggs
2021-03-18 1:47 ` [PATCH 1/2] audit: add support for the openat2 syscall Richard Guy Briggs
2021-03-18 10:48 ` Christian Brauner
2021-03-18 10:52 ` Christian Brauner
2021-03-18 12:03 ` Richard Guy Briggs
2021-03-18 12:08 ` Richard Guy Briggs
2021-04-23 2:34 ` Richard Guy Briggs
2021-04-23 7:48 ` Christian Brauner
2021-03-18 1:47 ` [PATCH 2/2] audit: add OPENAT2 record to list how Richard Guy Briggs
2021-03-18 10:49 ` Christian Brauner [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=20210318104932.5225mmecww2fd4zw@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rgb@redhat.com \
--cc=sgrubb@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).