From: Stephen Hemminger <stephen@networkplumber.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] bpf: indicate lderr when bpf_apply_relo_data fails
Date: Tue, 27 Jun 2017 16:09:39 -0700 [thread overview]
Message-ID: <20170627160939.236fae90@xeon-e3> (raw)
In-Reply-To: <e9c3ce47faaef896a30df16e72a9861ee59069dc.1498524386.git.daniel@iogearbox.net>
On Tue, 27 Jun 2017 02:48:36 +0200
Daniel Borkmann <daniel@iogearbox.net> wrote:
> When LLVM wrongly generates a rodata relo entry (llvm BZ #33599),
> then just bail out instead of probing for prog w/o reloc, which
> will fail in this case anyway.
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Applied, but don't you want a reasonable error message.
next prev parent reply other threads:[~2017-06-27 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 0:48 [PATCH iproute2] bpf: indicate lderr when bpf_apply_relo_data fails Daniel Borkmann
2017-06-27 23:09 ` Stephen Hemminger [this message]
2017-06-27 23:14 ` 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=20170627160939.236fae90@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=daniel@iogearbox.net \
--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).