From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: will.deacon@arm.com, arndb@arndb.de, patches@linaro.org
Subject: Re: [PATCH v3 0/4] audit(userspace): Improve arm/aarch64 support
Date: Wed, 19 Mar 2014 20:38:45 -0400 [thread overview]
Message-ID: <1673683.H2Z9NA5WsE@x2> (raw)
In-Reply-To: <1391410681-4924-1-git-send-email-takahiro.akashi@linaro.org>
On Monday, February 03, 2014 03:57:56 PM AKASHI Takahiro wrote:
> On ARM, endianness doesn't make any differences on auditing.
> See the discussion below:
> http://permalink.gmane.org/gmane.linux.ports.arm.kernel/165266
> In this version, mistakenly-used "ARMEB" and "armeb" are substituted
> with "ARM" and "arm" respectively in Patches [1,2/4].
>
> patch [3/4] adds more system call definitions for aarch64 (or arm64 in
> kernel) that are missing in the current implementation.
> https://www.redhat.com/archives/linux-audit/2013-November/msg00082.html
>
> Patch [4/4] enables auditing 32-bit tasks (ie. auditctl -F arch=b32) on
> aarch64.
>
> This code replies on my kernel patch for aarch64 support, and
> was tested on armv8 fast model with 32-bit/64-bit userland:
> 1) basic operations with auditctl/autrace
> # auditctl -a exit,always -S openat -F path=/etc/inittab
> # auditctl -a exit,always -F dir=/tmp -F perm=rw
> # auditctl -a task,always
> # autrace /bin/ls
> by comparing output from autrace with one from strace
>
> 2) audit-test-code (+ my workarounds for arm/arm64)
> by running "audit-tool", "filter" and "syscalls" test categories.
Thanks. This set of patches have been applied in svn. It would be good to
double check that arm still works for everyone. It does change --with-armeb
to --with-arm. This is something all distributions and testers would need to
fix in their build system.
Please let me know if there are any other updates needed.
-Steve
prev parent reply other threads:[~2014-03-20 0:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 7:28 [RFC PATH 0/2] audit(userspace): Add/Improve arm/aarch64 support AKASHI Takahiro
2013-11-19 7:28 ` [RFC PATCH 1/2] audit(userspace): Add missing syscalls for AArch64 AKASHI Takahiro
2013-11-19 7:29 ` [RFC PATCH 2/2] audit(userspace): Add arm LE/aarch64 BE support AKASHI Takahiro
2014-01-17 8:15 ` [PATCH v2 0/3] audit(userspace): Add/Improve arm/aarch64 support AKASHI Takahiro
2014-01-17 8:15 ` [PATCH v2 1/3] audit(userspace): Add missing syscalls for AArch64 AKASHI Takahiro
2014-01-17 8:15 ` [PATCH v2 2/3] audit(userspace): Add arm LE/aarch64 BE support AKASHI Takahiro
2014-01-17 8:15 ` [PATCH v2 3/3] audit(userspace): Add compat system call support for AArch64 AKASHI Takahiro
2014-01-17 15:05 ` Will Deacon
2014-01-20 5:05 ` AKASHI Takahiro
2014-02-03 6:57 ` [PATCH v3 0/4] audit(userspace): Improve arm/aarch64 support AKASHI Takahiro
2014-02-03 6:57 ` AKASHI Takahiro
2014-02-03 6:57 ` [PATCH v3 1/4] audit(userspace): Substitute ARMEB with ARM AKASHI Takahiro
2014-02-03 6:57 ` [PATCH v3 2/4] audit(userspace): Substitute armeb with arm AKASHI Takahiro
2014-02-03 6:58 ` [PATCH v3 3/4] audit(userspace): Add missing syscalls for AArch64 AKASHI Takahiro
2014-02-03 6:58 ` [PATCH v3 4/4] audit(userspace): Add compat system call support " AKASHI Takahiro
2014-03-20 0:38 ` Steve Grubb [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=1673683.H2Z9NA5WsE@x2 \
--to=sgrubb@redhat.com \
--cc=arndb@arndb.de \
--cc=linux-audit@redhat.com \
--cc=patches@linaro.org \
--cc=will.deacon@arm.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