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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 11 Sep 2014 21:54:09 +0200 From: Daniel Borkmann <dborkman@...hat.com> To: Alexei Starovoitov <ast@...mgrid.com> CC: Andy Lutomirski <luto@...capital.net>, "David S. Miller" <davem@...emloft.net>, Ingo Molnar <mingo@...nel.org>, Linus Torvalds <torvalds@...uxfoundation.org>, Steven Rostedt <rostedt@...dmis.org>, Hannes Frederic Sowa <hannes@...essinduktion.org>, Chema Gonzalez <chema@...gle.com>, Eric Dumazet <edumazet@...gle.com>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Pablo Neira Ayuso <pablo@...filter.org>, "H. Peter Anvin" <hpa@...or.com>, Andrew Morton <akpm@...uxfoundation.org>, Kees Cook <keescook@...omium.org>, Linux API <linux-api@...r.kernel.org>, Network Development <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v11 net-next 00/12] eBPF syscall, verifier, testsuite On 09/10/2014 10:21 PM, Alexei Starovoitov wrote: ... >>> char bpf_log_buf[LOG_BUF_SIZE]; >> >> What happens if the size isn't LOG_BUF_SIZE? > > would do you mean? > LOG_BUF_SIZE is just a user defined macro. > Can be anything. I believe, Andy means, what would happen if log_level > 0 but the log_size is not big enough so that the human-readable error text string from the verifier will fit into it? I presume that will be truncated then ... hm. > it's passed along with pointer: > .log_buf = bpf_log_buf, > .log_size = LOG_BUF_SIZE, > .log_level = 1, -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists