From: Kees Cook <keescook@chromium.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: linux-kernel@vger.kernel.org,
Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
Rich Felker <dalias@libc.org>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/seccomp: sh: Fix register names
Date: Tue, 17 Nov 2020 13:35:28 -0800 [thread overview]
Message-ID: <202011171334.3F1BDC484@keescook> (raw)
In-Reply-To: <921a7e36-8b58-4a59-029a-066f5a05859e@physik.fu-berlin.de>
On Tue, Nov 17, 2020 at 10:08:13PM +0100, John Paul Adrian Glaubitz wrote:
> Hi Kees!
>
> On 11/17/20 9:56 PM, Kees Cook wrote:
> > It looks like the seccomp selftests were never actually built for sh.
> > This fixes it, though I don't have an environment to do a runtime test
> > of it yet.
>
> We were testing libsecomp itself but I think we might have forgotten the
> self-test. Not sure how these are run.
If you're building natively, you can just build and run:
cd tools/testing/selftests/seccomp
make
./seccomp_bpf
--
Kees Cook
next prev parent reply other threads:[~2020-11-17 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 20:56 [PATCH] selftests/seccomp: sh: Fix register names Kees Cook
2020-11-17 21:08 ` John Paul Adrian Glaubitz
2020-11-17 21:35 ` Kees Cook [this message]
2020-11-17 21:41 ` John Paul Adrian Glaubitz
2020-11-17 22:57 ` John Paul Adrian Glaubitz
2020-11-20 19:05 ` 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=202011171334.3F1BDC484@keescook \
--to=keescook@chromium.org \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kernel@mkarcher.dialup.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--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