From: Daniel Borkmann <daniel@iogearbox.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] bpf: indicate lderr when bpf_apply_relo_data fails
Date: Wed, 28 Jun 2017 01:14:33 +0200 [thread overview]
Message-ID: <5952E6D9.3010201@iogearbox.net> (raw)
In-Reply-To: <20170627160939.236fae90@xeon-e3>
On 06/28/2017 01:09 AM, Stephen Hemminger wrote:
> 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.
Thanks, the error message in this case throws:
ELF contains non-map related relo data in entry <X> pointing to section <Y>! Compiler bug?!
prev parent reply other threads:[~2017-06-27 23:14 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
2017-06-27 23:14 ` Daniel Borkmann [this message]
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=5952E6D9.3010201@iogearbox.net \
--to=daniel@iogearbox.net \
--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).