From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] acpi: fix incompatibility with mcount-based function graph tracing
Date: Fri, 24 Mar 2017 13:12:54 -0500 [thread overview]
Message-ID: <20170324181254.gouyrbmppukrrbb6@treble> (raw)
In-Reply-To: <c6c72c7a0199bc79fdbe2318713e35d9@molgen.mpg.de>
On Tue, Mar 21, 2017 at 09:44:03PM +0100, Paul Menzel wrote:
> I checked out Linux 4.9.16, applied your patch on top, and copied the Debian
> 4.9 Linux kernel configuration, did `make menuconfig`, disabled building
> debugging symbols, and executed `ARCH=i386 make -j40 deb-pkg`.
>
> I installed that package on the Lenovo X60, and the result with tracing
> enabled has improved. The system suspends without a crash. Unfortunately,
> instead of resuming when pressing the power button, it starts from scratch.
> Suspend and resume without tracing enabled works though.
>
> I’ll try to collect logs, but I don’t know, if there will be any, if the
> system just resets.
>
> Maybe, this can be reproduced in QEMU?
So I was able to recreate this issue in qemu, and after some hours of
debugging I managed to figure it out.
It's rebooting during the resume because of a triple fault in
prepare_ftrace_return().
acpi wakeup for secondary cpu
startup_32_smp()
load_ucode_ap()
prepare_ftrace_return()
ftrace_graph_is_dead()
dereferences virtual address (kill_ftrace_graph) in real mode <-- BOOM
I tried fixing it by changing load_ucode_ap() to notrace, but that
function calls some other functions which also have mcount hooks, which
call other functions, etc.
Instead I was able to "fix" it by ignoring ftrace calls in real mode:
-----
index 8f3d9cf..5c0d0c6 100644
--- a/arch/x86/kernel/ftrace.c
+++ b/arch/x86/kernel/ftrace.c
@@ -983,6 +983,9 @@ void prepare_ftrace_return(unsigned long self_addr, unsigned long *parent,
unsigned long return_hooker = (unsigned long)
&return_to_handler;
+ if (__builtin_return_address(0) < TASK_SIZE_MAX)
+ return;
+
if (unlikely(ftrace_graph_is_dead()))
return;
---------------
I'm not sure what the best fix should really be. A few ideas off the
top of my head:
- A real mode check similar to the above (except it should probably be
more precise)
- Make tracing_graph_pause a percpu variable so that it can be read from
prepare_ftrace_return()
- pause_graph_tracing() from ftrace_suspend_notifier_call()
Steven, thoughts?
--
Josh
next prev parent reply other threads:[~2017-03-24 18:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 13:56 Josh Poimboeuf
2017-03-16 14:41 ` Steven Rostedt
2017-03-21 20:44 ` Paul Menzel
2017-03-22 0:04 ` Paul Menzel
2017-03-24 18:12 ` Josh Poimboeuf [this message]
2017-03-24 18:41 ` Steven Rostedt
2017-03-25 13:20 ` Rafael J. Wysocki
2017-03-27 14:08 ` Josh Poimboeuf
2017-03-27 14:54 ` [PATCH] ftrace/x86: fix x86-32 triple fault with graph tracing and suspend-to-ram Josh Poimboeuf
2017-03-27 15:01 ` Paul Menzel
2017-03-27 15:20 ` [PATCH v2] " Josh Poimboeuf
2017-03-27 15:24 ` [PATCH] " Steven Rostedt
2017-03-28 9:51 ` Paul Menzel
2017-03-28 15:39 ` Steven Rostedt
2017-03-28 15:55 ` Josh Poimboeuf
2017-03-28 21:12 ` Rafael J. Wysocki
2017-03-28 21:42 ` Josh Poimboeuf
2017-03-28 21:47 ` Rafael J. Wysocki
2017-03-27 16:59 ` [PATCH] acpi: fix incompatibility with mcount-based function graph tracing Rafael J. Wysocki
2017-03-26 20:57 [PATCH] trace: Make trace_hwlat timestamp y2038 safe Deepa Dinamani
2017-03-27 9:25 ` kbuild test robot
2017-03-27 9:55 ` Arnd Bergmann
2017-03-27 14:28 ` Steven Rostedt
2017-03-27 14:53 ` Arnd Bergmann
2017-03-27 15:30 ` Steven Rostedt
2017-03-27 15:35 ` Arnd Bergmann
2017-03-27 16:11 ` Steven Rostedt
2017-03-27 21:02 ` Deepa Dinamani
2017-03-28 7:26 ` Arnd Bergmann
2017-03-27 10:04 ` kbuild test robot
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=20170324181254.gouyrbmppukrrbb6@treble \
--to=jpoimboe@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®