From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexei Starovoitov Subject: Re: [PATCH v2 1/3] bpf: Use 1<<16 as ceiling for immediate alignment in verifier. Date: Fri, 19 May 2017 14:37:56 -0700 Message-ID: References: <7402a02c-cb00-d48e-1d2a-ccb03356fb72@solarflare.com> <20170519.164154.368589666756458942.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Cc: , , To: David Miller , Return-path: Received: from mx0a-00082601.pphosted.com ([67.231.145.42]:41315 "EHLO mx0a-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751573AbdESViW (ORCPT ); Fri, 19 May 2017 17:38:22 -0400 In-Reply-To: <20170519.164154.368589666756458942.davem@davemloft.net> Sender: netdev-owner@vger.kernel.org List-ID: On 5/19/17 1:41 PM, David Miller wrote: > From: Edward Cree > Date: Fri, 19 May 2017 18:17:42 +0100 > >> One question: is there a way to build the verifier as userland code >> (or at least as a module), or will I have to reboot every time I >> want to test a change? > > There currently is no such machanism, you will have to reboot every > time. > > I have considered working on making the code buildable outside of the > kernel. It shouldn't be too hard. it's not hard. We did it twice and both times abandoned. First time to have 'user space verifier' to check programs before loading and second time for fuzzing via llvm. Abandoned since it diverges very quickly from kernel.