Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1623477
| From | Josh Poimboeuf <jpoimboe@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v3] ftrace/x86/32: fix triple fault with graph tracing and suspend-to-ram |
| Date | 2017-04-14 04:20 +0200 |
| Message-ID | <tvZ05-3xy-1@gated-at.bofh.it> (permalink) |
| References | <tvVSx-1a3-11@gated-at.bofh.it> <tvW2d-1tc-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Apr 13, 2017 at 07:02:36PM -0400, Steven Rostedt wrote: > On Thu, 13 Apr 2017 17:53:55 -0500 > Josh Poimboeuf <jpoimboe@redhat.com> wrote: > > > On x86-32, with CONFIG_FIRMWARE and multiple CPUs, if you enable > > function graph tracing and then suspend to RAM, it will triple fault and > > reboot when it resumes. > > > > The first fault happens when booting a secondary CPU: > > > > startup_32_smp() > > load_ucode_ap() > > prepare_ftrace_return() > > ftrace_graph_is_dead() > > (accesses 'kill_ftrace_graph') > > > > The early head_32.S code calls into load_ucode_ap(), which has an an > > ftrace hook, so it calls prepare_ftrace_return(), which calls > > ftrace_graph_is_dead(), which tries to access the global > > 'kill_ftrace_graph' variable with a virtual address, causing a fault > > because the CPU is still in real mode. > > > > The fix is to add a check in prepare_ftrace_return() to make sure it's > > running in protected mode before continuing. The check makes sure the > > stack pointer is a virtual kernel address. It's a bit of a hack, but > > it's not very intrusive and it works well enough. > > > > For reference, here are a few other (more difficult) ways this could > > have potentially been fixed: > > > > - Move startup_32_smp()'s call to load_ucode_ap() down to *after* paging > > is enabled. (No idea what that would break.) > > > > - Track down load_ucode_ap()'s entire callee tree and mark all the > > functions 'notrace'. (Probably not realistic.) > > > > - Pause graph tracing in ftrace_suspend_notifier_call() or bringup_cpu() > > or __cpu_up(), and ensure that the pause facility can be queried from > > real mode. > > > > Reported-by: Paul Menzel <pmenzel@molgen.mpg.de> > > Tested-by: Paul Menzel <pmenzel@molgen.mpg.de> > > Cc: stable@kernel.org > > Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com> > > This is pretty much the same thing we were talking about before, right? Yeah, the same patch from before, now with more tags! > If so, then: > > Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Thanks! -- Josh
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v3] ftrace/x86/32: fix triple fault with graph tracing and suspend-to-ram Josh Poimboeuf <jpoimboe@redhat.com> - 2017-04-14 01:00 +0200
Re: [PATCH v3] ftrace/x86/32: fix triple fault with graph tracing and suspend-to-ram Steven Rostedt <rostedt@goodmis.org> - 2017-04-14 01:10 +0200
Re: [PATCH v3] ftrace/x86/32: fix triple fault with graph tracing and suspend-to-ram Josh Poimboeuf <jpoimboe@redhat.com> - 2017-04-14 04:20 +0200
[tip:x86/urgent] ftrace/x86: Fix triple fault with graph tracing and suspend-to-ram tip-bot for Josh Poimboeuf <tipbot@zytor.com> - 2017-04-14 12:00 +0200
csiph-web