live-patching.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Petr Mladek <pmladek@suse.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	live-patching@vger.kernel.org
Subject: Re: [GIT PULL] livepatching for 5.9-rc5
Date: Tue, 8 Sep 2020 13:32:39 -0500	[thread overview]
Message-ID: <20200908183239.vhy2txzcmlliul7d@treble> (raw)
In-Reply-To: <CAHk-=wiZUYjmPLiEaN5uHM4mGyYq8RBFvk=iZKkm9=8NxvcoZQ@mail.gmail.com>

On Tue, Sep 08, 2020 at 11:13:58AM -0700, Linus Torvalds wrote:
> Josh,
> 
> On Mon, Sep 7, 2020 at 1:20 AM Petr Mladek <pmladek@suse.com> wrote:
> >
> > - Workaround "unreachable instruction" objtool warnings that happen
> >   with some compiler versions.
> 
> I know I said this fixes things for me, but I just realized it doesn't entirely.
> 
> I wonder how I missed the remaining one:
> 
>    arch/x86/kvm/vmx/vmx.o: warning: objtool:
> vmx_handle_exit_irqoff()+0x142: unreachable instruction
> 
> so apparently gcc and objtool can still disagree even without that
> '-flive-patching'.
> 
> The unreachable code in question is after the call to
> handle_external_interrupt_irqoff(), and while that function is a bit
> odd, in this case I think it's objtool that is wrong.
> 
> I think that what happens is that the function doesn't have a 'ret'
> instruction, and instead returns by doing a tail-call to
> __sanitizer_cov_trace_pc with my config. And maybe that is what
> confuses objtool.
> 
> This is current tip-of-git of my tree, with a allmodconfig build (but
> the actual config will then depend on things like the gcc plugins
> being there too, so you may not get exactly the same thing as I do)
> 
> Josh? Am I missing something, and the objtool warning is valid? But
> yes, that code is doing some very very special stuff with that thunk
> call asm, so it's hard to read the asm.

Hm, I don't think I've seen that one.  We saw a similar warning in that
function before, but it was caused by the combination of
CONFIG_UBSAN_ALIGNMENT and CONFIG_UBSAN_TRAP, which I think Kees fixed.

Can you share the .o file?  At least I can't recreate with GCC 9.3.1,
which is all I have at the moment.

-- 
Josh


  reply	other threads:[~2020-09-08 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07  8:20 [GIT PULL] livepatching for 5.9-rc5 Petr Mladek
2020-09-08 18:13 ` Linus Torvalds
2020-09-08 18:32   ` Josh Poimboeuf [this message]
2020-09-08 18:42     ` Linus Torvalds
2020-09-08 20:59       ` Josh Poimboeuf
2020-09-08 18:16 ` pr-tracker-bot

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=20200908183239.vhy2txzcmlliul7d@treble \
    --to=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=torvalds@linux-foundation.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).