From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems compiling with KCFLAGS="-frecord-gcc-switches"
Date: Tue, 3 Oct 2017 13:00:23 -0500 [thread overview]
Message-ID: <20171003180022.at423kx22j5facpn@treble> (raw)
In-Reply-To: <20171003175457.GA21393@roeck-us.net>
On Tue, Oct 03, 2017 at 10:54:57AM -0700, Guenter Roeck wrote:
> Hi Josh,
>
> On Fri, Sep 29, 2017 at 03:46:09PM -0500, Josh Poimboeuf wrote:
> > On Fri, Sep 29, 2017 at 01:00:56PM -0700, Guenter Roeck wrote:
> > > Hi Josh,
> > >
> > > when trying to compile an image with KCFLAGS="-frecord-gcc-switches",
> > > I get the folllowing build warning/error.
> > >
> > > make allmodconfig
> > > KCFLAGS="-frecord-gcc-switches" make arch/x86/kvm/emulate.o
> > > ./tools/objtool/objtool check --no-unreachable "arch/x86/kvm/emulate.o"
> > >
> > > arch/x86/kvm/emulate.o: warning:
> > > objtool: .GCC.command.line+0x0: special: can't find new instruction
> > >
> > > Building a full image aborts with:
> > >
> > > WARNING: arch/x86/kvm/kvm.o(__ex_table+0x4c): Section mismatch in reference
> > > from the (unknown reference) (unknown)
> > > to the variable .GCC.command.line:kvm_fastop_exception
> > > FATAL: The relocation at __ex_table+0x4c references
> > > section ".GCC.command.line" which is not executable, IOW
> > > the kernel will fault if it ever tries to
> > > jump to it. Something is seriously wrong
> > > and should be fixed.
> > > make[2]: *** [arch/x86/kvm/kvm.o] Error 1
> > >
> > > Any idea what might cause this problem ?
> >
> > I think this is a GCC bug with the -frecord-gcc-switches feature. Due
> > to some ambiguity in some inline asm in emulate.c, it's placing some
> > kernel code in the .GCC.command.line section.
> >
> > This seems to fix it:
> >
> >
> > diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> > index a36254cbf776..d90cdc77e077 100644
> > --- a/arch/x86/kvm/emulate.c
> > +++ b/arch/x86/kvm/emulate.c
> > @@ -425,8 +425,10 @@ static int fastop(struct x86_emulate_ctxt *ctxt, void (*fop)(struct fastop *));
> > #op " %al \n\t" \
> > FOP_RET
> >
> > -asm(".global kvm_fastop_exception \n"
> > - "kvm_fastop_exception: xor %esi, %esi; ret");
> > +asm(".pushsection .fixup, \"ax\"\n"
> > + ".global kvm_fastop_exception \n"
> > + "kvm_fastop_exception: xor %esi, %esi; ret\n"
> > + ".popsection");
> >
> > FOP_START(setcc)
> > FOP_SETCC(seto)
>
> Do you plan to submit a patch for this, or do you want me to do it ?
Sorry, I've been juggling a bunch of other bugs. I'll submit it soon.
--
Josh
next prev parent reply other threads:[~2017-10-03 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 20:00 Guenter Roeck
2017-09-29 20:38 ` Guenter Roeck
2017-09-29 20:58 ` Josh Poimboeuf
2017-09-29 23:08 ` Guenter Roeck
2017-09-29 20:46 ` Josh Poimboeuf
2017-09-30 1:07 ` Guenter Roeck
2017-10-03 17:54 ` Guenter Roeck
2017-10-03 18:00 ` Josh Poimboeuf [this message]
2017-10-03 20:27 ` Guenter Roeck
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=20171003180022.at423kx22j5facpn@treble \
--to=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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®