public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Jiri Slaby <jslaby@suse.cz>, Jan Beulich <jbeulich@suse.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	rguenther@suse.de, stable <stable@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	X86 ML <x86@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH 1/1] x86/vdso: fix a reference to a non-existing instruction
Date: Fri, 6 Mar 2015 09:36:38 +0100	[thread overview]
Message-ID: <20150306083637.GA1320@gmail.com> (raw)
In-Reply-To: <CALCETrVwQ2VR1bqOBXxHwOsjaUqj0VS=kwYf5ZTYYzf3yW+iEA@mail.gmail.com>


* Andy Lutomirski <luto@amacapital.net> wrote:

> On Thu, Mar 5, 2015 at 12:13 AM, Jiri Slaby <jslaby@suse.cz> wrote:
> > .LSTARTFDEDLSI1 says:
> >         /* HACK: The dwarf2 unwind routines will subtract 1 from the
> >            return address to get an address in the middle of the
> >            presumed call instruction.  Since we didn't get here via
> >            a call, we need to include the nop before the real start
> >            to make up for it.  */
> >         .long .LSTART_sigreturn-1-.     /* PC-relative start address */
> >
> > But commit 69d0627a7f6e891189124d784d2fa90cae7c449a (x86 vDSO: reorder
> > vdso32 code) from 2.6.25 replaced
> >   .org __kernel_vsyscall+32,0x90
> > by ALIGN right before __kernel_sigreturn. Of course, ALIGN need not
> > generate any nop in there. Esp. gcc5 collapses vclock_gettime.o and
> > int80.o together with no generated nops as "ALIGN". In that case
> > kernel does not even link:
> > ld: .eh_frame_hdr table[4] FDE at 0000000000000648 overlaps table[5] FDE at 0000000000000670.
> >
> > So fix this by adding there at least a single nop and make the
> > function ALIGN possibly with more nops then.
> >
> > Kudos for reporting and diagnosing should go to Richard.
> >
> > Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> > Reported-by: Richard Biener <rguenther@suse.de>
> > Cc: stable@vger.kernel.org
> > Cc: Andy Lutomirski <luto@amacapital.net>
> > Cc: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: "H. Peter Anvin" <hpa@zytor.com>
> > Cc: x86@kernel.org
> > ---
> >  arch/x86/vdso/vdso32/sigreturn.S | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/x86/vdso/vdso32/sigreturn.S b/arch/x86/vdso/vdso32/sigreturn.S
> > index 31776d0efc8c..d7ec4e251c0a 100644
> > --- a/arch/x86/vdso/vdso32/sigreturn.S
> > +++ b/arch/x86/vdso/vdso32/sigreturn.S
> > @@ -17,6 +17,7 @@
> >         .text
> >         .globl __kernel_sigreturn
> >         .type __kernel_sigreturn,@function
> > +       nop /* this guy is needed for .LSTARTFDEDLSI1 below (watch for HACK) */
> >         ALIGN
> >  __kernel_sigreturn:
> >  .LSTART_sigreturn:
> 
> Acked-by: Andy Lutomirski <luto@amacapital.net>
> 
> Ingo or Thomas, can you apply this to tip:x86/urgent for this weekend?

Sure, I've applied it.

> Are we willing to depend on cfi-capable assemblers for 32-bit?  If 
> so, could we rewrite this garbage with .cfi directives?  The current 
> code is incomprehensible.

We could try, that code is certainly a mess. How much does that 
restrict our build compatibility?

Thanks,

	Ingo

  reply	other threads:[~2015-03-06  8:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05  8:13 [PATCH 1/1] x86/vdso: fix a reference to a non-existing instruction Jiri Slaby
2015-03-05 23:22 ` Andy Lutomirski
2015-03-06  8:36   ` Ingo Molnar [this message]
2015-03-06  8:39 ` [tip:x86/urgent] x86/vdso: Fix the build on GCC5 tip-bot for Jiri Slaby

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=20150306083637.GA1320@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jbeulich@suse.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=rguenther@suse.de \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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