mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: objtool warning breaks build for fs/dlm/lock.o
Date: Thu, 7 May 2020 18:29:41 -0500	[thread overview]
Message-ID: <20200507232941.jccuywl56bppxfyp@treble> (raw)
In-Reply-To: <CAK8P3a0QkqyA2wq_EbA+oWrLGgVdQwpBvb+G0aKyz60BOLs6fg@mail.gmail.com>

On Wed, May 06, 2020 at 04:07:25PM +0200, Arnd Bergmann wrote:
> Hi,
> 
> During randconfig testing with clang-10 I came across a number
> of additional objtool warnings, I'll send another mail about those
> when I have collected more information and some object files.
> 
> This one sticks out however, as objtool returns an error code that
> stops the build:

> fs/dlm/lock.o: warning: objtool: __receive_convert_reply()+0x1e5: can't find jump dest instruction at .text+0xcaa7

Thanks for sending the patch for this one.  Objtool always gets confused
by new compiler versions, I really think we need to revert
 
  644592d32837 ("objtool: Fail the kernel build on fatal errors")

because objtool is never going to be reliable enough such that we can be
confident that failing the build is the right thing to do.

-- 
Josh


  reply	other threads:[~2020-05-07 23:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 14:07 Arnd Bergmann
2020-05-07 23:29 ` Josh Poimboeuf [this message]
2020-05-08  9:27   ` Arnd Bergmann
2020-05-08  9:55     ` Peter Zijlstra
2020-05-08 16:17       ` Josh Poimboeuf
2020-05-08 16:26         ` Peter Zijlstra
2020-05-08 16:29           ` Josh Poimboeuf
2020-05-08  9:45   ` Peter Zijlstra
2020-05-08 16:20     ` Josh Poimboeuf
2020-05-18 19:57   ` Arnd Bergmann
2020-05-18 22:53     ` Josh Poimboeuf
2020-05-18 23:04       ` Josh Poimboeuf

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=20200507232941.jccuywl56bppxfyp@treble \
    --to=jpoimboe@redhat.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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®