From: Alexei Starovoitov <a...@fb.com> Date: Fri, 19 May 2017 14:37:56 -0700
> On 5/19/17 1:41 PM, David Miller wrote: >> From: Edward Cree <ec...@solarflare.com> >> 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. > Well, my idea was the create an environment in which kernel verifier.c could be built as-is. Maybe there would be some small compromises in verifier.c such as an ifdef test or two, but that should be it. It really is just a piece of what amounts to compiler infrastructure and not very kernel specific.
