s390/ftrace: prepare_ftrace_return() function call order
authorHeiko Carstens <heiko.carstens@de.ibm.com>
Fri, 11 Oct 2013 06:55:57 +0000 (08:55 +0200)
committerMartin Schwidefsky <schwidefsky@de.ibm.com>
Thu, 24 Oct 2013 15:17:03 +0000 (17:17 +0200)
commit05e0baaf9ba5a2d173c026530154388f0d2da72c
treee65a96f6a3e986b0b1f41a815dbb31721db24383
parent5ff4212f194f97b3a0f41745f231525c5c50dcbb
s390/ftrace: prepare_ftrace_return() function call order

Steven Rostedt noted that s390 is the only architecture which calls
ftrace_push_return_trace() before ftrace_graph_entry() and therefore has
the small advantage that trace.depth gets initialized automatically.

However this small advantage isn't worth the difference and possible subtle
breakage that may result from this.
So change s390 to have the same function call order like all other
architectures: first ftrace_graph_entry(), then ftrace_push_return_trace()

Reported-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
arch/s390/kernel/ftrace.c