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
| ||
|
Date: Tue, 25 Aug 2020 15:34:52 -0700 From: Alexei Starovoitov <alexei.starovoitov@...il.com> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: Daniel Borkmann <daniel@...earbox.net>, Alexei Starovoitov <ast@...nel.org>, Networking <netdev@...r.kernel.org>, Linux Next Mailing List <linux-next@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, David Miller <davem@...emloft.net> Subject: Re: linux-next: build failure after merge of the bpf-next tree On Tue, Aug 25, 2020 at 2:10 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote: > > Hi Alexei, > > On Tue, 25 Aug 2020 07:33:51 -0700 Alexei Starovoitov <alexei.starovoitov@...il.com> wrote: > > > > what do you suggest to use to make it 'manually enabled' ? > > All I could think of is to add: > > depends on !COMPILE_TEST > > so that allmodconfig doesn't pick it up. > > That is probably sufficient. Some gcc plugins and kasan bits, etc use > just that. Ok. Pushed the silencing 'fix': https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=2532f849b5134c4c62a20e5aaca33d9fb08af528
Powered by blists - more mailing lists