From: Eric Paris <eparis@redhat.com>
To: Will Drewry <wad@chromium.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Markus Gutschke <markus@chromium.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-doc@vger.kernel.org, kernel-hardening@lists.openwall.com,
netdev@vger.kernel.org, x86@kernel.org, arnd@arndb.de,
davem@davemloft.net, mingo@redhat.com, oleg@redhat.com,
peterz@infradead.org, rdunlap@xenotime.net,
mcgrathr@chromium.org, tglx@linutronix.de, luto@mit.edu,
serge.hallyn@canonical.com, djm@mindrot.org,
scarybeasts@gmail.com, indan@nul.nu, pmoore@redhat.com,
akpm@linux-foundation.org, corbet@lwn.net,
eric.dumazet@gmail.com, keescook@chromium.org
Subject: Re: [PATCH v8 3/8] seccomp: add system call filtering using BPF
Date: Thu, 16 Feb 2012 19:50:09 -0500 [thread overview]
Message-ID: <1329439809.2337.32.camel@localhost> (raw)
In-Reply-To: <CABqD9hZd41AWZub+wxGWwxJtGWfk+pVWQhn7DM_0q0tS9r_wDA@mail.gmail.com>
On Thu, 2012-02-16 at 17:00 -0600, Will Drewry wrote:
> On Thu, Feb 16, 2012 at 4:06 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> > On 02/16/2012 01:51 PM, Will Drewry wrote:
> Then syscall_namespace(current, regs) returns
> * 0 - SYSCALL_NS_32 (for existing 32 and config_compat)
> * 1 - SYSCALL_NS_64 (for existing 64 bit)
> * 2 - SYSCALL_NS_X32 (everything after 2 is arch specific)
> * ..
>
> This patch series is pegged to x86 right now, so it's not a big deal
> to add a simple syscall_namespace to asm/syscall.h. Of course, the
> code is always the easy part. Even easier would be to only assign 0
> and 1 in the seccomp_data for 32-bit or 64-bit, then leave the rest of
> the u32 untouched until x32 stabilizes and the TS_COMPAT interactions
> are sorted.
I don't know if anyone cares, but include/linux/audit.h tries to expose
this type of information so audit userspace can later piece things back
together. (we get this info from the syscall entry exit code so we know
which arch it is).
Not sure how x32 is hoping to expose its syscall info, but others are
going to have the same/similar problem.
-Eric
next prev parent reply other threads:[~2012-02-17 0:50 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 20:02 [PATCH v8 1/8] sk_run_filter: add support for custom load_pointer Will Drewry
2012-02-16 20:02 ` [PATCH v8 2/8] seccomp: kill the seccomp_t typedef Will Drewry
2012-02-20 2:55 ` James Morris
2012-02-16 20:02 ` [PATCH v8 3/8] seccomp: add system call filtering using BPF Will Drewry
2012-02-16 20:06 ` H. Peter Anvin
2012-02-16 20:25 ` Will Drewry
2012-02-16 21:17 ` H. Peter Anvin
2012-02-16 21:28 ` Markus Gutschke
2012-02-16 21:34 ` H. Peter Anvin
2012-02-16 21:51 ` Will Drewry
2012-02-16 22:06 ` H. Peter Anvin
2012-02-16 23:00 ` Will Drewry
2012-02-17 0:23 ` Andrew Lutomirski
2012-02-17 0:43 ` H. Peter Anvin
2012-02-17 0:50 ` Eric Paris [this message]
2012-02-17 2:24 ` H. Peter Anvin
2012-02-17 3:53 ` Will Drewry
2012-02-17 4:12 ` H. Peter Anvin
2012-02-17 4:26 ` Will Drewry
2012-02-17 4:32 ` H. Peter Anvin
2012-02-17 4:40 ` Will Drewry
2012-02-16 21:31 ` Will Drewry
2012-02-17 0:48 ` Indan Zupancic
2012-02-17 0:51 ` Andrew Lutomirski
2012-02-17 1:10 ` H. Peter Anvin
2012-02-17 1:25 ` Indan Zupancic
2012-02-17 1:33 ` H. Peter Anvin
2012-02-17 2:00 ` Indan Zupancic
2012-02-17 2:16 ` Andrew Lutomirski
2012-02-17 2:22 ` H. Peter Anvin
2012-02-17 3:27 ` Indan Zupancic
2012-02-17 4:09 ` H. Peter Anvin
2012-02-17 4:51 ` Indan Zupancic
2012-02-17 2:44 ` Indan Zupancic
2012-02-17 3:38 ` [kernel-hardening] " Will Drewry
2012-02-16 20:02 ` [PATCH v8 4/8] seccomp: add SECCOMP_RET_ERRNO Will Drewry
2012-02-16 20:02 ` [PATCH v8 5/8] seccomp: Add SECCOMP_RET_TRAP Will Drewry
[not found] ` <CAE6n16mCrJC=Sre+PT1H_VfSjW0MGyi0xtEcdcRvGMvvwXWzmA@mail.gmail.com>
2012-02-16 20:28 ` Markus Gutschke
2012-02-16 21:23 ` H. Peter Anvin
2012-02-16 20:42 ` Will Drewry
2012-02-16 21:11 ` [PATCH v9 " Will Drewry
2012-02-16 21:11 ` [PATCH v9 8/8] Documentation: prctl/seccomp_filter Will Drewry
2012-02-16 21:28 ` [PATCH v8 5/8] seccomp: Add SECCOMP_RET_TRAP H. Peter Anvin
2012-02-16 21:33 ` Will Drewry
2012-02-16 20:02 ` [PATCH v8 6/8] ptrace,seccomp: Add PTRACE_SECCOMP support Will Drewry
2012-02-17 5:08 ` Indan Zupancic
2012-02-17 16:23 ` Will Drewry
2012-02-17 22:55 ` Indan Zupancic
2012-02-21 17:31 ` Will Drewry
2012-02-16 20:02 ` [PATCH v8 7/8] x86: Enable HAVE_ARCH_SECCOMP_FILTER Will Drewry
2012-02-16 20:02 ` [PATCH v8 8/8] Documentation: prctl/seccomp_filter Will Drewry
2012-02-16 20:08 ` [PATCH v8 1/8] sk_run_filter: add support for custom load_pointer Will Drewry
2012-02-17 1:54 ` Joe Perches
2012-02-17 2:22 ` Will Drewry
2012-02-17 3:04 ` Indan Zupancic
2012-02-17 4:13 ` Will Drewry
2012-02-17 5:05 ` Indan Zupancic
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=1329439809.2337.32.camel@localhost \
--to=eparis@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=djm@mindrot.org \
--cc=eric.dumazet@gmail.com \
--cc=hpa@zytor.com \
--cc=indan@nul.nu \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=markus@chromium.org \
--cc=mcgrathr@chromium.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=pmoore@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=scarybeasts@gmail.com \
--cc=serge.hallyn@canonical.com \
--cc=tglx@linutronix.de \
--cc=wad@chromium.org \
--cc=x86@kernel.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).