From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [libseccomp-discuss] ARM audit, seccomp, etc are broken wrt OABI syscalls
Date: Wed, 6 Nov 2013 15:51:04 +0000 [thread overview]
Message-ID: <20131106155104.GZ16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1383751951.28218.64.camel@flatline.rdu.redhat.com>
On Wed, Nov 06, 2013 at 10:32:31AM -0500, Eric Paris wrote:
> On Tue, 2013-11-05 at 14:36 -0800, Andy Lutomirski wrote:
> > 1. Set a different audit arch for OABI syscalls (e.g.
> > AUDIT_ARCH_ARMOABI). That is, treat OABI syscall entries the same way
> > that x86_64 treats int 80.
>
> As the audit maintainer, I like #1. It might break ABI, but the ABI is
> flat wrong now and not maintainable...
If you read the whole thread, you will see that this corner case is just
not worth the effort to support. Audit may as well be disabled by
kernel config if any OABI support is enabled.
next prev parent reply other threads:[~2013-11-06 15:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 22:36 ARM audit, seccomp, etc are broken wrt OABI syscalls Andy Lutomirski
2013-11-06 0:14 ` Kees Cook
2013-11-06 0:40 ` Russell King - ARM Linux
2013-11-06 3:22 ` Andy Lutomirski
2013-11-07 12:55 ` Henrique de Moraes Holschuh
2013-11-07 17:54 ` Kees Cook
2013-11-07 19:04 ` Henrique de Moraes Holschuh
2013-11-06 9:52 ` Mikael Pettersson
2013-11-06 22:30 ` Matt Sealey
2013-11-06 22:33 ` Andy Lutomirski
2013-11-06 15:32 ` [libseccomp-discuss] " Eric Paris
2013-11-06 15:51 ` Russell King - ARM Linux [this message]
2013-11-06 21:20 ` Will Drewry
2013-11-06 21:26 ` Kees Cook
2013-11-06 21:49 ` Andy Lutomirski
2013-11-06 22:17 ` Russell King - ARM Linux
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=20131106155104.GZ16735@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).