From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: rostedt@goodmis.org, colin.king@canonical.com,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps to it" has been added to the 4.4-stable tree
Date: Fri, 20 Jan 2017 10:43:35 +0100 [thread overview]
Message-ID: <20170120094335.GB27345@kroah.com> (raw)
In-Reply-To: <492e3143-b15a-a467-15b2-5c544e870613@suse.cz>
On Fri, Jan 20, 2017 at 10:17:57AM +0100, Jiri Slaby wrote:
> On 01/06/2017, 03:55 PM, gregkh@linuxfoundation.org wrote:
> > From 847fa1a6d3d00f3bdf68ef5fa4a786f644a0dd67 Mon Sep 17 00:00:00 2001
> > From: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
> > Date: Thu, 8 Dec 2016 12:48:26 -0500
> > Subject: ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps to it
> >
> > From: Steven Rostedt (Red Hat) <rostedt@goodmis.org>
> >
> > commit 847fa1a6d3d00f3bdf68ef5fa4a786f644a0dd67 upstream.
> >
> > With new binutils, gcc may get smart with its optimization and change a jmp
> > from a 5 byte jump to a 2 byte one even though it was jumping to a global
> > function. But that global function existed within a 2 byte radius, and gcc
> > was able to optimize it. Unfortunately, that jump was also being modified
> > when function graph tracing begins. Since ftrace expected that jump to be 5
> > bytes, but it was only two, it overwrote code after the jump, causing a
> > crash.
> >
> > This was fixed for x86_64 with commit 8329e818f149, with the same subject as
> > this commit, but nothing was done for x86_32.
>
> Greg,
>
> can we have the x86_64 fix (8329e818f149) in 4.4 too?
Ah, yes, I totally missed that. I'll queue it up after this next round
of kernels goes out in a few hours.
thanks,
greg k-h
prev parent reply other threads:[~2017-01-20 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 14:55 Patch "ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short jumps to it" has been added to the 4.4-stable tree gregkh
2017-01-20 9:17 ` Jiri Slaby
2017-01-20 9:43 ` Greg KH [this message]
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=20170120094335.GB27345@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=colin.king@canonical.com \
--cc=jslaby@suse.cz \
--cc=rostedt@goodmis.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.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).