From: tycho at tycho.ws (Tycho Andersen)
Subject: [PATCH] selftests/seccomp: Abort without user notification support
Date: Wed, 16 Jan 2019 17:46:50 -0700 [thread overview]
Message-ID: <20190117004650.GB17449@cisco> (raw)
In-Reply-To: <20190117003525.GA37918@beast>
On Wed, Jan 16, 2019 at 04:35:25PM -0800, Kees Cook wrote:
> In the face of missing user notification support, the self test needs
> to stop executing a test (ASSERT_*) instead of just reporting and
> continuing (EXPECT_*). This adjusts the user notification tests to do
> that where needed.
>
> Reported-by: Shuah Khan <shuah at kernel.org>
> Fixes: 6a21cc50f0c7 ("seccomp: add a return code to trap to userspace")
The gift that keeps on giving :)
Reviewed-by: Tycho Andersen <tycho at tycho.ws>
Thanks,
Tycho
WARNING: multiple messages have this Message-ID (diff)
From: tycho@tycho.ws (Tycho Andersen)
Subject: [PATCH] selftests/seccomp: Abort without user notification support
Date: Wed, 16 Jan 2019 17:46:50 -0700 [thread overview]
Message-ID: <20190117004650.GB17449@cisco> (raw)
Message-ID: <20190117004650.IVgRnQWBjQK2APJIq_Bz64O9lXX7vGcEbPc9kwaDOHE@z> (raw)
In-Reply-To: <20190117003525.GA37918@beast>
On Wed, Jan 16, 2019@04:35:25PM -0800, Kees Cook wrote:
> In the face of missing user notification support, the self test needs
> to stop executing a test (ASSERT_*) instead of just reporting and
> continuing (EXPECT_*). This adjusts the user notification tests to do
> that where needed.
>
> Reported-by: Shuah Khan <shuah at kernel.org>
> Fixes: 6a21cc50f0c7 ("seccomp: add a return code to trap to userspace")
The gift that keeps on giving :)
Reviewed-by: Tycho Andersen <tycho at tycho.ws>
Thanks,
Tycho
WARNING: multiple messages have this Message-ID (diff)
From: Tycho Andersen <tycho@tycho.ws>
To: Kees Cook <keescook@chromium.org>
Cc: Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
James Morris <jmorris@namei.org>
Subject: Re: [PATCH] selftests/seccomp: Abort without user notification support
Date: Wed, 16 Jan 2019 17:46:50 -0700 [thread overview]
Message-ID: <20190117004650.GB17449@cisco> (raw)
In-Reply-To: <20190117003525.GA37918@beast>
On Wed, Jan 16, 2019 at 04:35:25PM -0800, Kees Cook wrote:
> In the face of missing user notification support, the self test needs
> to stop executing a test (ASSERT_*) instead of just reporting and
> continuing (EXPECT_*). This adjusts the user notification tests to do
> that where needed.
>
> Reported-by: Shuah Khan <shuah@kernel.org>
> Fixes: 6a21cc50f0c7 ("seccomp: add a return code to trap to userspace")
The gift that keeps on giving :)
Reviewed-by: Tycho Andersen <tycho@tycho.ws>
Thanks,
Tycho
next prev parent reply other threads:[~2019-01-17 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 0:35 [PATCH] selftests/seccomp: Abort without user notification support keescook
2019-01-17 0:35 ` Kees Cook
2019-01-17 0:35 ` Kees Cook
2019-01-17 0:46 ` tycho [this message]
2019-01-17 0:46 ` Tycho Andersen
2019-01-17 0:46 ` Tycho Andersen
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=20190117004650.GB17449@cisco \
--to=unknown@example.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.