All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Kees Cook <keescook@chromium.org>, Robert Sesek <rsesek@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests/seccomp: Be more precise with syscall arguments.
Date: Mon, 2 Nov 2015 13:09:51 -0700	[thread overview]
Message-ID: <5637C30F.70001@osg.samsung.com> (raw)
In-Reply-To: <CAGXu5j+41UTPkvAArwUjA+BHv3S+55iHEb40BF1=m7_5g-NkHQ@mail.gmail.com>

On 11/02/2015 12:49 PM, Kees Cook wrote:
> On Mon, Nov 2, 2015 at 10:50 AM, Robert Sesek <rsesek@google.com> wrote:
>> Certain syscall emulation layers strictly check that the number of
>> arguments match what the syscall handler expects. The KILL_one_arg_one and
>> KILL_one_arg_six tests passed more parameters than expected to various
>> syscalls, causing failures in this emulation mode. Instead, test using
>> syscalls that take the appropriate number of arguments.
>>
>> Signed-off-by: Robert Sesek <rsesek@google.com>
> 
> Signed-off-by: Kees Cook <keescook@chromium.org>
> 
> Looks great, thanks!
> 
> Shuah, can you take this into the selftests tree?
> 

Robert,

Could you please send this patch to me. It didn't make to
my Inbox.

thanks,
-- Shuah

-- 
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978

  reply	other threads:[~2015-11-02 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 18:50 [PATCH] selftests/seccomp: Be more precise with syscall arguments Robert Sesek
2015-11-02 19:49 ` Kees Cook
2015-11-02 20:09   ` Shuah Khan [this message]
2015-11-02 20:32     ` Robert Sesek
2015-11-02 21:43       ` Shuah Khan

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=5637C30F.70001@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rsesek@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.