From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Subject: Re: [PATCH RFC net-next 08/14] bpf: add eBPF verifier Date: Sat, 28 Jun 2014 18:58:50 -0700 Message-ID: References: <1403913966-4927-1-git-send-email-ast@plumgrid.com> <1403913966-4927-9-git-send-email-ast@plumgrid.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: Sender: netdev-owner@vger.kernel.org To: Alexei Starovoitov Cc: "David S. Miller" , Ingo Molnar , Linus Torvalds , Steven Rostedt , Daniel Borkmann , Chema Gonzalez , Eric Dumazet , Peter Zijlstra , Arnaldo Carvalho de Melo , Jiri Olsa , Thomas Gleixner , "H. Peter Anvin" , Andrew Morton , Kees Cook , Linux API , Network Development , "linux-kernel@vger.kernel.org" List-Id: linux-api@vger.kernel.org On Sat, Jun 28, 2014 at 1:25 PM, Alexei Starovoitov wrote: > On Sat, Jun 28, 2014 at 9:01 AM, Andy Lutomirski wrote: >> On Fri, Jun 27, 2014 at 5:06 PM, Alexei Starovoitov wrote: >>> Safety of eBPF programs is statically determined by the verifier, which detects: >> >> This is a very high-level review. I haven't tried to read all the >> code yet, and this is mostly questions rather than real comments. > > These were great questions! I hope I answered them. If not, please > continue asking. I have plenty more questions, but here's one right now: does anything prevent programs from using pointers in comparisons, returning pointers, or otherwise figuring out the value of a pointer? If so, I think it would be worthwhile to prevent that so that eBPF programs can't learn kernel addresses. --Andy