From: David Miller <davem@davemloft.net>
To: ast@fb.com
Cc: ecree@solarflare.com, daniel@iogearbox.net,
alexei.starovoitov@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/3] bpf: Use 1<<16 as ceiling for immediate alignment in verifier.
Date: Fri, 19 May 2017 19:16:15 -0400 (EDT) [thread overview]
Message-ID: <20170519.191615.136362788931426782.davem@davemloft.net> (raw)
In-Reply-To: <a4a1fe92-fa35-1d3f-1b3c-e094d715db2c@fb.com>
From: Alexei Starovoitov <ast@fb.com>
Date: Fri, 19 May 2017 14:37:56 -0700
> On 5/19/17 1:41 PM, David Miller wrote:
>> From: Edward Cree <ecree@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.
next prev parent reply other threads:[~2017-05-19 23:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 16:04 [PATCH v2 1/3] bpf: Use 1<<16 as ceiling for immediate alignment in verifier David Miller
2017-05-16 12:37 ` Edward Cree
2017-05-16 19:52 ` David Miller
2017-05-16 22:53 ` Alexei Starovoitov
2017-05-17 14:00 ` Edward Cree
2017-05-17 15:33 ` Edward Cree
2017-05-18 0:16 ` David Miller
2017-05-18 1:18 ` Alexei Starovoitov
2017-05-18 14:10 ` Edward Cree
2017-05-18 2:48 ` Alexei Starovoitov
2017-05-18 14:49 ` Edward Cree
2017-05-18 16:38 ` Edward Cree
2017-05-18 18:41 ` Edward Cree
2017-05-19 1:22 ` Alexei Starovoitov
2017-05-19 14:21 ` Edward Cree
2017-05-19 14:55 ` Alexei Starovoitov
2017-05-19 17:17 ` Edward Cree
2017-05-19 20:00 ` Alignment in BPF verifier Edward Cree
2017-05-19 20:39 ` David Miller
2017-05-19 23:05 ` Daniel Borkmann
2017-05-23 14:41 ` Edward Cree
2017-05-23 17:43 ` Edward Cree
2017-05-23 23:59 ` Alexei Starovoitov
2017-05-23 19:45 ` Alexei Starovoitov
2017-05-23 21:27 ` Daniel Borkmann
2017-05-24 13:46 ` Edward Cree
2017-05-24 16:39 ` Alexei Starovoitov
2017-05-25 16:31 ` David Miller
2017-05-19 20:48 ` David Miller
2017-05-19 20:41 ` [PATCH v2 1/3] bpf: Use 1<<16 as ceiling for immediate alignment in verifier David Miller
2017-05-19 21:37 ` Alexei Starovoitov
2017-05-19 23:16 ` David Miller [this message]
2017-05-20 0:20 ` Alexei Starovoitov
2017-05-17 16:13 ` David Miller
2017-05-17 17:00 ` Edward Cree
2017-05-17 17:25 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170519.191615.136362788931426782.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=ecree@solarflare.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).