From: Shuah Khan <shuahkh@osg.samsung.com>
To: Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Willeke <willeke@linux.vnet.ibm.com>,
heicars2@linux.vnet.ibm.com,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests/seccomp: add support for s390
Date: Wed, 9 Sep 2015 10:45:04 -0600 [thread overview]
Message-ID: <55F06210.7050103@osg.samsung.com> (raw)
In-Reply-To: <CAGXu5jK6ZWw0wrEC1jZkfZ_aBdTbnLQLxktwsPhMfN2TBWuRFw@mail.gmail.com>
On 09/09/2015 10:40 AM, Kees Cook wrote:
> Re-ping. Can someone pull this into their tree?
>
> -Kees
>
> On Fri, Aug 21, 2015 at 11:22 AM, Kees Cook <keescook@chromium.org> wrote:
>> This adds support for s390 to the seccomp selftests. Some improvements
>> were made to enhance the accuracy of failure reporting, and additional
>> tests were added to validate assumptions about the currently traced
>> syscall. Also adds early asserts for running on older kernels to avoid
>> noise when the seccomp syscall is not implemented.
>>
>> Signed-off-by: Kees Cook <keescook@chromium.org>
>> ---
Sorry looks like it got lost in my LinuxCon backlog. I will queue it
up for 4.3-rc1.
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2015-09-09 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 18:22 [PATCH] selftests/seccomp: add support for s390 Kees Cook
2015-09-09 16:40 ` Kees Cook
2015-09-09 16:45 ` Shuah Khan [this message]
2015-09-09 16:56 ` Shuah Khan
2015-09-09 17:23 ` Kees Cook
2015-09-09 18:46 ` Shuah Khan
2015-09-14 22:53 ` Shuah Khan
2015-09-10 9:11 ` Michael Ellerman
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=55F06210.7050103@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=heicars2@linux.vnet.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=wad@chromium.org \
--cc=willeke@linux.vnet.ibm.com \
/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