From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-kernel@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH] audit syscall classes
Date: Thu, 6 Jul 2006 09:42:44 +0200 [thread overview]
Message-ID: <20060706074244.GA9416@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <200607011800.k61I02nV022260@hera.kernel.org>
On Sat, Jul 01, 2006 at 06:00:02PM +0000, Linux Kernel Mailing List wrote:
> commit b915543b46a2aa599fdd2169e51bcfd88812a12b
> tree 8025e6654829d4c245b5b6b6f47a84543ebffb7b
> parent 6e5a2d1d32596850a0ebf7fb3e54c0d69901dabd
> author Al Viro <viro@zeniv.linux.org.uk> Sat, 01 Jul 2006 11:56:16 -0400
> committer Al Viro <viro@zeniv.linux.org.uk> Sat, 01 Jul 2006 15:44:10 -0400
>
> [PATCH] audit syscall classes
>
> Allow to tie upper bits of syscall bitmap in audit rules to kernel-defined
> sets of syscalls. Infrastructure, a couple of classes (with 32bit counterparts
> for biarch targets) and actual tie-in on i386, amd64 and ia64.
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
>
> arch/i386/kernel/Makefile | 1
> arch/i386/kernel/audit.c | 23 ++++++++++++++++++
> arch/ia64/ia32/Makefile | 1
> arch/ia64/ia32/audit.c | 11 +++++++++
> arch/ia64/kernel/Makefile | 1
> arch/ia64/kernel/audit.c | 29 +++++++++++++++++++++++
> arch/x86_64/ia32/Makefile | 3 ++
> arch/x86_64/ia32/audit.c | 11 +++++++++
> arch/x86_64/kernel/Makefile | 1
> arch/x86_64/kernel/audit.c | 29 +++++++++++++++++++++++
> include/asm-generic/audit_change_attr.h | 18 ++++++++++++++
> include/asm-generic/audit_dir_write.h | 14 +++++++++++
> include/linux/audit.h | 7 +++++
> kernel/auditfilter.c | 39 ++++++++++++++++++++++++++++++++
> 14 files changed, 188 insertions(+)
Excuse my ignorance, but this looks like every architecture needs to add
something like this. If it is needed, is there some easy way to test the
implementation?
parent reply other threads:[~2006-07-06 7:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200607011800.k61I02nV022260@hera.kernel.org>]
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=20060706074244.GA9416@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=viro@ftp.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
all inboxes | Powered by JetHome®