netdev - Re: [PATCH bpf-next] selftests/bpf: missing headers test_lwt

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] [day] [month] [year] [list]

Message-ID: <CAKSCvkROaq3=QgsPsDA7WyTO0=rB9MoFQKL9rLkuP56Qewvzsg@mail.gmail.com>
Date:   Sat, 26 May 2018 14:26:24 +0200
From:   Mathieu Xhonneux <m.xhonneux@...il.com>
To:     Daniel Borkmann <daniel@...earbox.net>
Cc:     Alexei Starovoitov <alexei.starovoitov@...il.com>,
        netdev <netdev@...r.kernel.org>, Y Song <ys114321@...il.com>
Subject: Re: [PATCH bpf-next] selftests/bpf: missing headers test_lwt_seg6local

2018-05-25 18:39 GMT+02:00 Daniel Borkmann <daniel@...earbox.net>:
> Yes, should definitely go there to tools include infrastructure.

What is the point of tools/testing/selftests/bpf/include/uapi/ then ?
Incompatibility issues preventing linux/types.h to be included in
non-bpf testing executables ? My initial conception was that all
headers only related to bpf should go into this directory. Sending a
v2.