linux-kernel - Re: clang --target=bpf missing on f23 was: Re: [PATCH 1/2] perf test: Add libbpf relocation checker

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 22 Jan 2016 18:56:02 +0100
From:	Daniel Borkmann <daniel@...earbox.net>
To:	Adam Jackson <ajax@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Alexei Starovoitov <alexei.starovoitov@...il.com>
CC:	Wang Nan <wangnan0@...wei.com>, ast@...nel.org,
	linux-kernel@...r.kernel.org, Li Zefan <lizefan@...wei.com>,
	pi3orama@....com, Dave Airlie <airlied@...hat.com>
Subject: Re: clang --target=bpf missing on f23 was:  Re: [PATCH 1/2] perf
 test: Add libbpf relocation checker

On 01/22/2016 06:35 PM, Adam Jackson wrote:
> On Fri, 2016-01-22 at 14:22 -0300, Arnaldo Carvalho de Melo wrote:
>
>> 	the 'bpf' target for clang is being used together with perf to
>> build scriptlets into object code that then gets uploaded to the kernel
>> via sys_bpf(), was the decision not to include 'bpf' just an accident?
>
> I wouldn't call it a "decision", that would imply intent. The main
> reason I explicitly list targets for llvm is to limit the CPU backends
> to arches Fedora actually runs on (which itself is because I really
> only care about llvmpipe, and am only touching llvm because it's in my
> way). Had no idea there was a bpf backend, so never thought to enable
> it.
>
> llvm-3.7.0-4.fc2{3,4} are building now with the bpf backend enabled,
> I'll create an update for F23 when it's built.

Awesome, thanks!