On Fri, Jan 29, 2016 at 08:59:36AM -0500, Steven Rostedt wrote:
> On Fri, 29 Jan 2016 13:57:49 +0100
> Heiko Carstens <heiko.carstens@xxxxxxxxxx> wrote:
>
> > Surpringly it wasn't one of my own patches which broke the stack tracer on
> > s390, but one from Steven:
> >
> > 72ac426a5bb0 ("tracing: Clean up stack tracing and fix fentry updates")
> >
> > Now I only need to figure out why :)
>
> Try this one?
>
> 7717c6be699975f6733d278b13b7c4295d73caf6
> tracing: Fix stacktrace skip depth in trace_buffer_unlock_commit_regs()
>
> Or at the very least, merge with Linus's latest and see if something
> else doesn't fix it.
No, that doesn't fix it (current Linus' master):
# uname -a
Linux p2345007 4.5.0-rc1-00032-g26cd83670f2f #26 SMP Fri Jan 29 15:39:47 CET 2016 s390x s390x s390x GNU/Linux
# cat stack_max_size
4496
# cat stack_trace
Depth Size Location (0 entries)
----- ---- --------
--
To unsubscribe from this list: send the line "unsubscribe linux-s390" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
