From: Richard Guy Briggs <rgb@redhat.com> To: Linux-Audit Mailing List <linux-audit@redhat.com>, LKML <linux-kernel@vger.kernel.org> Cc: Paul Moore <paul@paul-moore.com>, Eric Paris <eparis@parisplace.org>, Steve Grubb <sgrubb@redhat.com>, Richard Guy Briggs <rgb@redhat.com>, Alexander Viro <viro@zeniv.linux.org.uk>, Eric Paris <eparis@redhat.com>, linux-fsdevel@vger.kernel.org Subject: [PATCH 0/2] audit: add support for openat2 Date: Wed, 17 Mar 2021 21:47:16 -0400 [thread overview] Message-ID: <cover.1616031035.git.rgb@redhat.com> (raw) 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 Richard Guy Briggs (2): audit: add support for the openat2 syscall audit: add OPENAT2 record to list how arch/alpha/kernel/audit.c | 2 ++ arch/ia64/kernel/audit.c | 2 ++ arch/parisc/kernel/audit.c | 2 ++ arch/parisc/kernel/compat_audit.c | 2 ++ arch/powerpc/kernel/audit.c | 2 ++ arch/powerpc/kernel/compat_audit.c | 2 ++ arch/s390/kernel/audit.c | 2 ++ arch/s390/kernel/compat_audit.c | 2 ++ arch/sparc/kernel/audit.c | 2 ++ arch/sparc/kernel/compat_audit.c | 2 ++ arch/x86/ia32/audit.c | 2 ++ arch/x86/kernel/audit_64.c | 2 ++ fs/open.c | 2 ++ include/linux/audit.h | 10 ++++++++++ include/uapi/linux/audit.h | 1 + kernel/audit.h | 2 ++ kernel/auditsc.c | 19 +++++++++++++++++++ lib/audit.c | 4 ++++ lib/compat_audit.c | 4 ++++ 19 files changed, 66 insertions(+) -- 2.27.0
WARNING: multiple messages have this Message-ID (diff)
From: Richard Guy Briggs <rgb@redhat.com> To: Linux-Audit Mailing List <linux-audit@redhat.com>, LKML <linux-kernel@vger.kernel.org> Cc: Richard Guy Briggs <rgb@redhat.com>, Alexander Viro <viro@zeniv.linux.org.uk>, linux-fsdevel@vger.kernel.org, Eric Paris <eparis@parisplace.org> Subject: [PATCH 0/2] audit: add support for openat2 Date: Wed, 17 Mar 2021 21:47:16 -0400 [thread overview] Message-ID: <cover.1616031035.git.rgb@redhat.com> (raw) 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 Richard Guy Briggs (2): audit: add support for the openat2 syscall audit: add OPENAT2 record to list how arch/alpha/kernel/audit.c | 2 ++ arch/ia64/kernel/audit.c | 2 ++ arch/parisc/kernel/audit.c | 2 ++ arch/parisc/kernel/compat_audit.c | 2 ++ arch/powerpc/kernel/audit.c | 2 ++ arch/powerpc/kernel/compat_audit.c | 2 ++ arch/s390/kernel/audit.c | 2 ++ arch/s390/kernel/compat_audit.c | 2 ++ arch/sparc/kernel/audit.c | 2 ++ arch/sparc/kernel/compat_audit.c | 2 ++ arch/x86/ia32/audit.c | 2 ++ arch/x86/kernel/audit_64.c | 2 ++ fs/open.c | 2 ++ include/linux/audit.h | 10 ++++++++++ include/uapi/linux/audit.h | 1 + kernel/audit.h | 2 ++ kernel/auditsc.c | 19 +++++++++++++++++++ lib/audit.c | 4 ++++ lib/compat_audit.c | 4 ++++ 19 files changed, 66 insertions(+) -- 2.27.0 -- Linux-audit mailing list Linux-audit@redhat.com https://listman.redhat.com/mailman/listinfo/linux-audit
next reply other threads:[~2021-03-18 1:49 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-18 1:47 Richard Guy Briggs [this message] 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 1:47 ` Richard Guy Briggs 2021-03-18 1:47 ` Richard Guy Briggs 2021-03-18 1:47 ` Richard Guy Briggs 2021-03-18 1:47 ` Richard Guy Briggs 2021-03-18 10:48 ` Christian Brauner 2021-03-18 10:48 ` Christian Brauner 2021-03-18 10:48 ` Christian Brauner 2021-03-18 10:48 ` Christian Brauner 2021-03-18 10:52 ` Christian Brauner 2021-03-18 10:52 ` Christian Brauner 2021-03-18 10:52 ` Christian Brauner 2021-03-18 10:52 ` Christian Brauner 2021-03-18 12:03 ` Richard Guy Briggs 2021-03-18 12:03 ` Richard Guy Briggs 2021-03-18 12:03 ` Richard Guy Briggs 2021-03-18 12:03 ` Richard Guy Briggs 2021-03-18 12:03 ` Richard Guy Briggs 2021-03-18 12:08 ` Richard Guy Briggs 2021-03-18 12:08 ` Richard Guy Briggs 2021-03-18 12:08 ` Richard Guy Briggs 2021-03-18 12:08 ` Richard Guy Briggs 2021-03-18 12:08 ` Richard Guy Briggs 2021-04-23 2:34 ` Richard Guy Briggs 2021-04-23 2:34 ` Richard Guy Briggs 2021-04-23 2:34 ` Richard Guy Briggs 2021-04-23 2:34 ` Richard Guy Briggs 2021-04-23 7:48 ` Christian Brauner 2021-04-23 7:48 ` Christian Brauner 2021-04-23 7:48 ` Christian Brauner 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 1:47 ` Richard Guy Briggs 2021-03-18 10:49 ` [PATCH 0/2] audit: add support for openat2 Christian Brauner 2021-03-18 10:49 ` Christian Brauner
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=cover.1616031035.git.rgb@redhat.com \ --to=rgb@redhat.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=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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.