From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Luis Ressel <aranea@aixah.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
open list <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] objtool: Don't use -Werror
Date: Fri, 5 Apr 2019 09:39:26 -0500 [thread overview]
Message-ID: <20190405143926.wmrkjsazlheeg6qs@treble> (raw)
In-Reply-To: <20190405142443.rgpwbgyym76xizad@vega.skynet.aixah.de>
On Fri, Apr 05, 2019 at 04:24:43PM +0200, Luis Ressel wrote:
> On Fri, Apr 05, 2019 at 07:39:09AM -0500, Josh Poimboeuf wrote:
> > What version of libelf are you using? AFAIK, the non-elfutils version
> > of libelf is buggy and has been unmaintained for 10 years.
>
> I'm using libelf 0.8.13, which is indeed 10y old, abandoned and rather
> suboptimal (elfutils OTOH is nonportable, and I haven't gotten around
> yet to fixing its incompatibilities with the musl libc).
If you can't use the elfutils version, I'd recommend just disabling all
the features which rely on objtool. Because some of the libelf-related
bugs I've seen are pretty bad, and we rely on objtool for some pretty
fundamental things like ORC oops stack traces and live patching.
In fact I think we probably need a patch to fail the build if the
10-year-old libelf is used, as I've gotten several bug reports there and
the answer is always the same ("don't use old libelf").
> I can accept that you might not be interested in fixing issues related
> to libelf, but using -Werror is a more general problem which just
> happens to be triggered by my particular setup.
Hm, I would actually argue the reverse. Warnings are generally bad and
-Werror is useful for ensuring that we don't have any. For warnings
that don't provide value, we just disable those individual warnings.
--
Josh
next prev parent reply other threads:[~2019-04-05 14:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 11:01 Luis Ressel
2019-04-05 12:39 ` Josh Poimboeuf
2019-04-05 14:24 ` Luis Ressel
2019-04-05 14:39 ` Josh Poimboeuf [this message]
2019-04-05 16:05 ` Luis Ressel
2019-04-05 16:15 ` Josh Poimboeuf
2019-04-05 16:30 ` Luis Ressel
2019-04-05 16:16 ` David Laight
2019-04-05 16:21 ` Josh Poimboeuf
2019-04-05 16:35 ` David Laight
2019-04-05 17:12 ` Josh Poimboeuf
2019-04-05 17:17 ` David Laight
2019-04-05 17:22 ` Josh Poimboeuf
2019-04-08 9:20 ` David Laight
2019-04-08 13:02 ` Josh Poimboeuf
2019-04-05 16:26 ` 'Luis Ressel'
2019-04-05 16:35 ` 'Luis Ressel'
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=20190405143926.wmrkjsazlheeg6qs@treble \
--to=jpoimboe@redhat.com \
--cc=aranea@aixah.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stable@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
all inboxes | Powered by JetHome®