From: "Mickaël Salaün" <mic@digikod.net>
To: linux-kernel@vger.kernel.org
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Jonathan Corbet" <corbet@lwn.net>,
"Jeff Dike" <jdike@addtoit.com>,
"Richard Weinberger" <richard@nod.at>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, "Kees Cook" <keescook@chromium.org>,
"Andy Lutomirski" <luto@amacapital.net>,
"Will Drewry" <wad@chromium.org>,
"Shuah Khan" <shuahkh@osg.samsung.com>,
"Chris Metcalf" <cmetcalf@ezchip.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Andrew Morton" <akpm@linux-foundation.org>,
"James Hogan" <james.hogan@imgtec.com>,
"Thomas Meyer" <thomas@m3y3r.de>,
"Nicolas Iooss" <nicolas.iooss_linux@m4x.org>,
"Anton Ivanov" <aivanov@brocade.com>,
linux-doc@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net,
linux-api@vger.kernel.org,
"Meredydd Luff" <meredydd@senatehouse.o>
Subject: [PATCH v2 0/4] um: Add seccomp support
Date: Mon, 21 Dec 2015 20:29:19 +0100 [thread overview]
Message-ID: <1450726163-8399-1-git-send-email-mic@digikod.net> (raw)
This series add seccomp support to User-mode Linux (i386 and x86_64
subarchitectures) and fix ptrace issues. This apply on v4.4-rc4 and pass all
the 48 tests from selftest/seccomp plus the UML ptsc test.
Changes since v1; addressed Richard Weinberger's comments:
* fix a new PTRACE_SETREGS bug on x86_64 [1/4]
* fix an old PTRACE_SETREGS bug when updating orig_ax on i386 [1/4]
Regards,
Mickaël
Mickaël Salaün (4):
um: Fix ptrace GETREGS/SETREGS bugs
selftests/seccomp: Remove the need for HAVE_ARCH_TRACEHOOK
um: Add full asm/syscall.h support
um: Add seccomp support
.../seccomp/seccomp-filter/arch-support.txt | 2 +-
arch/um/Kconfig.common | 1 +
arch/um/Kconfig.um | 16 +++
arch/um/include/asm/syscall-generic.h | 138 +++++++++++++++++++++
arch/um/include/asm/thread_info.h | 2 +
arch/um/kernel/skas/syscall.c | 30 +++--
arch/um/os-Linux/skas/process.c | 7 --
arch/x86/um/asm/syscall.h | 1 +
arch/x86/um/ptrace_32.c | 8 +-
tools/testing/selftests/seccomp/seccomp_bpf.c | 27 +++-
10 files changed, 205 insertions(+), 27 deletions(-)
create mode 100644 arch/um/include/asm/syscall-generic.h
--
2.6.4
next reply other threads:[~2015-12-21 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 19:29 Mickaël Salaün [this message]
2015-12-21 19:29 ` [PATCH v2 1/4] um: Fix ptrace GETREGS/SETREGS bugs Mickaël Salaün
2015-12-21 19:29 ` [PATCH v2 2/4] selftests/seccomp: Remove the need for HAVE_ARCH_TRACEHOOK Mickaël Salaün
2015-12-21 20:26 ` [PATCH v2 3/4] um: Add full asm/syscall.h support Mickaël Salaün
2015-12-21 20:30 ` [PATCH v2 4/4] um: Add seccomp support Mickaël Salaün
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=1450726163-8399-1-git-send-email-mic@digikod.net \
--to=mic@digikod.net \
--cc=aivanov@brocade.com \
--cc=akpm@linux-foundation.org \
--cc=cmetcalf@ezchip.com \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=james.hogan@imgtec.com \
--cc=jdike@addtoit.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=meredydd@senatehouse.o \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=nicolas.iooss_linux@m4x.org \
--cc=richard@nod.at \
--cc=shuahkh@osg.samsung.com \
--cc=tglx@linutronix.de \
--cc=thomas@m3y3r.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
--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).