From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: SECCOMP support
Date: Sat, 25 Sep 2010 19:58:05 +0100 [thread overview]
Message-ID: <20100925185805.GB3044@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1009251220420.13233@xanadu.home>
On Sat, Sep 25, 2010 at 12:31:07PM -0400, Nicolas Pitre wrote:
> Well, for one thing, the syscall tracing has the ability to change the
> actual syscall number. So this looked like a possible hole that could
> somehow be exploited to escape the seccomp control. So I went with the
> safest way.
That is also true for x86 - the seccomp test on x86 is done first,
before the syscall entry trap.
next prev parent reply other threads:[~2010-09-25 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 21:11 [PATCH] ARM: SECCOMP support Nicolas Pitre
2010-09-25 11:34 ` Russell King - ARM Linux
2010-09-25 16:31 ` Nicolas Pitre
2010-09-25 18:58 ` Russell King - ARM Linux [this message]
2010-09-25 19:46 ` Nicolas Pitre
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=20100925185805.GB3044@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