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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 27 Jan 2020 12:09:47 +0100
From:   Daniel Borkmann <>
To:     Toke Høiland-Jørgensen <>,
        Palmer Dabbelt <>,,,
        Jesper Dangaard Brouer <>
Subject: Re: [PATCH] selftests/bpf: Elide a check for LLVM versions that can't
 compile it

On 1/24/20 9:27 PM, Toke Høiland-Jørgensen wrote:
> Palmer Dabbelt <> writes:
>> The current stable LLVM BPF backend fails to compile the BPF selftests
>> due to a compiler bug.  The bug has been fixed in trunk, but that fix
>> hasn't landed in the binary packages I'm using yet (Fedora arm64).
>> Without this workaround the tests don't compile for me.
>> This patch triggers a preprocessor warning on LLVM versions that
>> definitely have the bug.  The test may be conservative (ie, I'm not sure
>> if 9.1 will have the fix), but it should at least make the current set
>> of stable releases work together.
>> See for more information on the fix.  I
>> obtained the workaround from
>> Fixes: 20a9ad2e7136 ("selftests/bpf: add CO-RE relocs array tests")
>> Signed-off-by: Palmer Dabbelt <>
> Having to depend on the latest trunk llvm to compile the selftests is
> definitely unfortunate. I believe there are some tests that won't work
> at all without trunk llvm (the fentry/fexit stuff comes to mind;
> although I'm not sure if they'll fail to compile, just fail to run?).
> Could we extend this type of checking to any such case?

Yeah, Palmer, are you saying that with this fix you're able to run through
all of the BPF test suite on bpf-next with clang/llvm 9.0?

So far policy has been that tests run always on latest trunk to also cover
llvm changes in BPF backend to make sure there are no regressions there. OT:
perhaps we should have a 'make deps' target in BPF selftests to make it easier
for developers to spin up a latest test env to run selftests in.

Powered by blists - more mailing lists