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: Fri, 13 Mar 2015 19:27:41 -0700 From: Alexei Starovoitov <ast@...mgrid.com> To: Daniel Borkmann <daniel@...earbox.net>, "David S. Miller" <davem@...emloft.net> CC: Thomas Graf <tgraf@...g.ch>, linux-api@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v2 net-next 1/2] bpf: allow extended BPF programs access skb fields On 3/13/15 7:16 PM, Daniel Borkmann wrote: > On 03/14/2015 03:08 AM, Alexei Starovoitov wrote: >> On 3/13/15 7:06 PM, Daniel Borkmann wrote: >>> On 03/14/2015 02:46 AM, Daniel Borkmann wrote: >>> ... >>>> Previously, it was much more consistent, which I like better. And only >>>> because of the simple BUILD_BUG_ON()? :/ >>> >>> Alternative is to move all of them into a central place, something like >>> in twsk_build_assert() or __mld2_query_bugs[]. >> >> nope. that defeats the purpose of bug_on. > > Well, it doesn't. ;) It throws a build error thus the user is forced to > investigate that further. according to this distorted logic all build_bug_on can be in one file across the whole tree, since 'user is forced to investigate' ?! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists