stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	stable@kernel.org, Alistair Strachan <astrachan@google.com>,
	Florian Weimer <fweimer@redhat.com>,
	Carlos O'Donell <carlos@redhat.com>,
	"H. J. Lu" <hjl.tools@gmail.com>, Borislav Petkov <bp@suse.de>,
	Laura Abbott <labbott@redhat.com>,
	Andy Lutomirski <luto@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	kernel-team@android.com, stable <stable@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>, X86 ML <x86@kernel.org>
Subject: Re: [PATCH for 4.4, 4.9 and 4.14] x86/vdso: Pass --eh-frame-hdr to the linker
Date: Tue, 14 May 2019 08:32:49 -0400	[thread overview]
Message-ID: <20190514123249.GK11972@sasha-vm> (raw)
In-Reply-To: <20190514075004.GD27017@kroah.com>

On Tue, May 14, 2019 at 09:50:04AM +0200, Greg Kroah-Hartman wrote:
>On Tue, May 14, 2019 at 04:34:29PM +0900, Nobuhiro Iwamatsu wrote:
>> From: Alistair Strachan <astrachan@google.com>
>>
>> commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 upstream.
>>
>> Commit
>>
>>   379d98ddf413 ("x86: vdso: Use $LD instead of $CC to link")
>>
>> accidentally broke unwinding from userspace, because ld would strip the
>> .eh_frame sections when linking.
>>
>> Originally, the compiler would implicitly add --eh-frame-hdr when
>> invoking the linker, but when this Makefile was converted from invoking
>> ld via the compiler, to invoking it directly (like vmlinux does),
>> the flag was missed. (The EH_FRAME section is important for the VDSO
>> shared libraries, but not for vmlinux.)
>>
>> Fix the problem by explicitly specifying --eh-frame-hdr, which restores
>> parity with the old method.
>>
>> See relevant bug reports for additional info:
>>
>>   https://bugzilla.kernel.org/show_bug.cgi?id=201741
>>   https://bugzilla.redhat.com/show_bug.cgi?id=1659295
>>
>> Fixes: 379d98ddf413 ("x86: vdso: Use $LD instead of $CC to link")
>> Reported-by: Florian Weimer <fweimer@redhat.com>
>> Reported-by: Carlos O'Donell <carlos@redhat.com>
>> Reported-by: "H. J. Lu" <hjl.tools@gmail.com>
>> Signed-off-by: Alistair Strachan <astrachan@google.com>
>> Signed-off-by: Borislav Petkov <bp@suse.de>
>> Tested-by: Laura Abbott <labbott@redhat.com>
>> Cc: Andy Lutomirski <luto@kernel.org>
>> Cc: Carlos O'Donell <carlos@redhat.com>
>> Cc: "H. Peter Anvin" <hpa@zytor.com>
>> Cc: Ingo Molnar <mingo@redhat.com>
>> Cc: Joel Fernandes <joel@joelfernandes.org>
>> Cc: kernel-team@android.com
>> Cc: Laura Abbott <labbott@redhat.com>
>> Cc: stable <stable@vger.kernel.org>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: X86 ML <x86@kernel.org>
>> Link: https://lkml.kernel.org/r/20181214223637.35954-1-astrachan@google.com
>> Signed-off-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
>> ---
>>  arch/x86/entry/vdso/Makefile | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>
>This is already in the 4.14 stable queue.
>
>Sasha, how did you tools miss it for 4.4 and 4.9?

This commit claims it fixes 379d98ddf413 ("x86: vdso: Use $LD instead of
$CC to link"), which is not in 4.9 nor 4.4, nor does 379d98ddf413 apply
cleanly to 4.9 or 4.4, and neither does the backport of 379d98ddf413
for 4.14 provided to us by the google folks. That's how :)

--
Thanks,
Sasha

  reply	other threads:[~2019-05-14 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14  7:34 [PATCH for 4.4, 4.9 and 4.14] x86/vdso: Pass --eh-frame-hdr to the linker Nobuhiro Iwamatsu
2019-05-14  7:50 ` Greg Kroah-Hartman
2019-05-14 12:32   ` Sasha Levin [this message]
2019-05-14 12:39     ` Greg Kroah-Hartman
2019-05-14 12:56       ` Sasha Levin
2019-05-14 13:22         ` Greg Kroah-Hartman
2019-05-15  0:25   ` Nathan Chancellor
2019-05-15 16:07     ` Sasha Levin

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=20190514123249.GK11972@sasha-vm \
    --to=sashal@kernel.org \
    --cc=astrachan@google.com \
    --cc=bp@suse.de \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hjl.tools@gmail.com \
    --cc=hpa@zytor.com \
    --cc=joel@joelfernandes.org \
    --cc=kernel-team@android.com \
    --cc=labbott@redhat.com \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=stable@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).