From: Daniel Borkmann <daniel@iogearbox.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, ast@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] bpf: make jited programs visible in traces
Date: Tue, 21 Feb 2017 02:27:18 +0100 [thread overview]
Message-ID: <58AB9776.6090401@iogearbox.net> (raw)
In-Reply-To: <58AB3E79.7040307@iogearbox.net>
On 02/20/2017 08:07 PM, Daniel Borkmann wrote:
> On 02/20/2017 08:05 PM, Eric Dumazet wrote:
> [...]
>> Latest net-next tree dies on my hosts, and my bisection came to this
>> commit.
>
> Thanks for the report, I'll take a look!
Fyi, fix will come tomorrow.
next prev parent reply other threads:[~2017-02-21 1:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 21:24 [PATCH net-next 0/3] Misc BPF improvements Daniel Borkmann
2017-02-16 21:24 ` [PATCH net-next 1/3] bpf: mark all registered map/prog types as __ro_after_init Daniel Borkmann
2017-02-16 21:24 ` [PATCH net-next 2/3] bpf: remove stubs for cBPF from arch code Daniel Borkmann
2017-02-16 21:24 ` [PATCH net-next 3/3] bpf: make jited programs visible in traces Daniel Borkmann
2017-02-20 19:05 ` Eric Dumazet
2017-02-20 19:07 ` Daniel Borkmann
2017-02-21 1:27 ` Daniel Borkmann [this message]
2017-02-17 18:40 ` [PATCH net-next 0/3] Misc BPF improvements 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=58AB9776.6090401@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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.