From: Will Deacon <will@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Keno Fischer <keno@juliacomputing.com>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>, Oleg Nesterov <oleg@redhat.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-next/seccomp 0/3] Check ENOSYS under tracing
Date: Fri, 10 Jul 2020 13:40:33 +0100 [thread overview]
Message-ID: <20200710124033.GA30458@willie-the-truck> (raw)
In-Reply-To: <20200705061232.4151319-1-keescook@chromium.org>
On Sat, Jul 04, 2020 at 11:12:29PM -0700, Kees Cook wrote:
> This expands the seccomp selftest to poke a architectural behavior corner
> that Keno Fischer noticed[1]. In the process, I took the opportunity
> to do the kselftest harness variant refactoring I'd been meaning to do,
> which made adding this test much nicer.
>
> I'd prefer this went via the seccomp tree, as it builds on top of the
> other recent seccomp feature addition tests. Testing and reviews are
> welcome! :)
Thanks! I tested these on arm64 (qemu) and they helped me to find a bug
in some patches I was writing.
Tested-by: Will Deacon <will@kernel.org>
Will
next prev parent reply other threads:[~2020-07-10 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 6:12 Kees Cook
2020-07-05 6:12 ` [PATCH 1/3] selftests/harness: Clean up kern-doc for fixtures Kees Cook
2020-07-05 16:53 ` Jakub Kicinski
2020-07-05 6:12 ` [PATCH 2/3] selftests/seccomp: Refactor to use fixture variants Kees Cook
2020-07-05 16:53 ` Jakub Kicinski
2020-07-05 6:12 ` [PATCH 3/3] selftests/seccomp: Check ENOSYS under tracing Kees Cook
2020-07-05 7:01 ` Kees Cook
2020-07-10 12:40 ` Will Deacon [this message]
2020-07-10 16:11 ` [PATCH for-next/seccomp 0/3] " Kees Cook
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=20200710124033.GA30458@willie-the-truck \
--to=will@kernel.org \
--cc=keescook@chromium.org \
--cc=keno@juliacomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=shuah@kernel.org \
--cc=wad@chromium.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
all inboxes | Powered by JetHome®