linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Mickaël Salaün" <mic@digikod.net>, linux-kernel@vger.kernel.org
Cc: Jeff Dike <jdike@addtoit.com>,
	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>,
	user-mode-linux-devel@lists.sourceforge.net,
	Meredydd Luff <meredydd@senatehouse.org>,
	David Drysdale <drysdale@google.com>
Subject: Re: [PATCH v3 0/4] um: Add seccomp support
Date: Sun, 10 Jan 2016 21:18:26 +0100	[thread overview]
Message-ID: <5692BC92.1010605@nod.at> (raw)
In-Reply-To: <1451421347-9468-1-git-send-email-mic@digikod.net>

Am 29.12.2015 um 21:35 schrieb Mickaël Salaün:
> This series add seccomp support to User-mode Linux (i386 and x86_64
> subarchitectures) and fix ptrace issues. This apply on v4.4-rc7 and pass all
> the 48 tests from selftest/seccomp plus the UML ptsc test.
> 
> Changes since v2:
> * remove get_syscall() from os.h and don't include it in syscall.c [1/4]
> * rebase to v4.4-rc7
> 
> 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

Applied!

Thanks,
//richard


      parent reply	other threads:[~2016-01-10 20:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-29 20:35 [PATCH v3 0/4] um: Add seccomp support Mickaël Salaün
2015-12-29 20:35 ` [PATCH v3 1/4] um: Fix ptrace GETREGS/SETREGS bugs Mickaël Salaün
2015-12-29 20:35 ` [PATCH v3 2/4] selftests/seccomp: Remove the need for HAVE_ARCH_TRACEHOOK Mickaël Salaün
2015-12-29 20:35 ` [PATCH v3 3/4] um: Add full asm/syscall.h support Mickaël Salaün
2015-12-29 20:35 ` [PATCH v3 4/4] um: Add seccomp support Mickaël Salaün
2016-01-04 20:13 ` [PATCH v3 0/4] " Kees Cook
2016-01-06 14:15   ` David Drysdale
2016-01-06 14:18     ` Richard Weinberger
2016-01-10 20:18 ` Richard Weinberger [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=5692BC92.1010605@nod.at \
    --to=richard@nod.at \
    --cc=aivanov@brocade.com \
    --cc=akpm@linux-foundation.org \
    --cc=cmetcalf@ezchip.com \
    --cc=drysdale@google.com \
    --cc=hpa@zytor.com \
    --cc=james.hogan@imgtec.com \
    --cc=jdike@addtoit.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=meredydd@senatehouse.org \
    --cc=mic@digikod.net \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=nicolas.iooss_linux@m4x.org \
    --cc=shuahkh@osg.samsung.com \
    --cc=tglx@linutronix.de \
    --cc=thomas@m3y3r.de \
    --cc=user-mode-linux-devel@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).