linux-kernel - Re: [PATCH] selftests/seccomp: sh: Fix register names

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <202011171334.3F1BDC484@keescook>
Date:   Tue, 17 Nov 2020 13:35:28 -0800
From:   Kees Cook <keescook@...omium.org>
To:     John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Cc:     linux-kernel@...r.kernel.org,
        Michael Karcher <kernel@...rcher.dialup.fu-berlin.de>,
        Rich Felker <dalias@...c.org>,
        Andy Lutomirski <luto@...capital.net>,
        Will Drewry <wad@...omium.org>, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH] selftests/seccomp: sh: Fix register names

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