From: Jakub Kicinski <kubakici@wp.pl>
To: David Ahern <dsahern@gmail.com>
Cc: Alexei Starovoitov <ast@fb.com>, Martin KaFai Lau <kafai@fb.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com
Subject: Re: [PATCH v2 net-next 0/8] Introduce bpf ID
Date: Thu, 1 Jun 2017 12:00:38 -0700 [thread overview]
Message-ID: <20170601120038.680c8169@cakuba.lan> (raw)
In-Reply-To: <5e8b1713-0220-5c53-210d-8040efd36cfb@gmail.com>
On Thu, 1 Jun 2017 12:52:28 -0600, David Ahern wrote:
> On 6/1/17 12:27 PM, Alexei Starovoitov wrote:
> > 'I want to retrieve original instructions' is not a problem. It's a
> > push for 'solution'. Explaining 'why' you want to see original
> > instructions would describe the actual problem.
>
> I have explained this.
>
> You are creating this hyper-complex almost completely invisible
> infrastructure. You are enabling binary blobs that can bypass the
> network stack and modify packets with almost no introspection on what is
> happening. BPF code can from a variety of sources -- OS vendors,
> upstream repos, 3rd party vendors (eg., H/W vendors), and "in-house"
> development. Each will swear to the end that any observed problem is not
> with their code. In my experience, it falls on to the OS and kernel
> experts to figure out why Linux is breaking something. To do that we
> need tools to look at what code is running where and something that can
> be used in production environments not requiring a disruption to the
> service that the box is providing.
Forgive my ignorance, but is it possible to dump code of a loaded
module out of the kernel?
next prev parent reply other threads:[~2017-06-01 19:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 18:58 [PATCH v2 net-next 0/8] Introduce bpf ID Martin KaFai Lau
2017-05-31 18:58 ` [PATCH v2 net-next 1/8] bpf: Introduce bpf_prog ID Martin KaFai Lau
2017-05-31 18:58 ` [PATCH v2 net-next 2/8] bpf: Introduce bpf_map ID Martin KaFai Lau
2017-05-31 18:58 ` [PATCH v2 net-next 3/8] bpf: Add BPF_(PROG|MAP)_GET_NEXT_ID command Martin KaFai Lau
2017-05-31 18:58 ` [PATCH v2 net-next 4/8] bpf: Add BPF_PROG_GET_FD_BY_ID Martin KaFai Lau
2017-05-31 18:58 ` [PATCH v2 net-next 5/8] bpf: Add BPF_MAP_GET_FD_BY_ID Martin KaFai Lau
2017-05-31 18:59 ` [PATCH v2 net-next 6/8] bpf: Add jited_len to struct bpf_prog Martin KaFai Lau
2017-05-31 18:59 ` [PATCH v2 net-next 7/8] bpf: Add BPF_OBJ_GET_INFO_BY_FD Martin KaFai Lau
2017-05-31 18:59 ` [PATCH v2 net-next 8/8] bpf: Test for bpf ID Martin KaFai Lau
2017-05-31 23:35 ` [PATCH v2 net-next 0/8] Introduce " David Miller
2017-06-03 1:08 ` Martin KaFai Lau
2017-06-01 2:22 ` Jakub Kicinski
2017-06-01 13:55 ` David Ahern
2017-06-01 17:24 ` Alexei Starovoitov
2017-06-01 17:51 ` David Ahern
2017-06-01 18:27 ` Alexei Starovoitov
2017-06-01 18:33 ` David Miller
2017-06-01 18:57 ` Jakub Kicinski
2017-06-01 18:52 ` David Ahern
2017-06-01 18:56 ` David Miller
2017-06-01 19:00 ` Jakub Kicinski [this message]
2017-06-01 21:48 ` Alexei Starovoitov
2017-06-02 11:39 ` David Ahern
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=20170601120038.680c8169@cakuba.lan \
--to=kubakici@wp.pl \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=kafai@fb.com \
--cc=kernel-team@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.