From: Daniel Borkmann <daniel@iogearbox.net>
To: stephen@networkplumber.org
Cc: ast@fb.com, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH iproute2 master 0/2] Minor BPF updates
Date: Fri, 21 Jul 2017 21:13:05 +0200 [thread overview]
Message-ID: <cover.1500663605.git.daniel@iogearbox.net> (raw)
Two minor updates to the BPF code, first one makes use of the
recently exposed owner_jited in fdinfo to report whether a
load issue related to tail calls occured, and second one fixes
up custom mount of bpf fs when passed via env.
Thanks!
Daniel Borkmann (2):
bpf: improve error reporting around tail calls
bpf: fix mnt path when from env
lib/bpf.c | 281 +++++++++++++++++++++++++++++++++++++++++++++++---------------
1 file changed, 214 insertions(+), 67 deletions(-)
--
1.9.3
next reply other threads:[~2017-07-21 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 19:13 Daniel Borkmann [this message]
2017-07-21 19:13 ` [PATCH iproute2 master 1/2] bpf: improve error reporting around tail calls Daniel Borkmann
2017-07-21 23:28 ` Stephen Hemminger
2017-07-22 8:06 ` Daniel Borkmann
2017-07-21 19:13 ` [PATCH iproute2 master 2/2] bpf: fix mnt path when from env Daniel Borkmann
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=cover.1500663605.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@fb.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).