From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Pratyush Anand <panand@redhat.com>,
schwidefsky@de.ibm.com, linux-s390@vger.kernel.org,
Chunyu Hu <chuhu@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] s390:ftrace: add save_stack_trace_regs()
Date: Fri, 29 Jan 2016 15:45:22 +0100 [thread overview]
Message-ID: <20160129144522.GE3896@osiris> (raw)
In-Reply-To: <20160129085936.09458371@gandalf.local.home>
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@de.ibm.com> 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)
----- ---- --------
next prev parent reply other threads:[~2016-01-29 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 5:20 [PATCH] s390:ftrace: add save_stack_trace_regs() Pratyush Anand
2016-01-29 5:20 ` Pratyush Anand
2016-01-29 8:54 ` Heiko Carstens
2016-01-29 12:57 ` Heiko Carstens
2016-01-29 13:59 ` Steven Rostedt
2016-01-29 14:45 ` Heiko Carstens [this message]
2016-01-29 15:22 ` Steven Rostedt
2016-01-29 16:49 ` Heiko Carstens
2016-01-29 16:56 ` Steven Rostedt
2016-01-29 17:12 ` Heiko Carstens
2016-02-01 9:00 ` Heiko Carstens
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=20160129144522.GE3896@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=chuhu@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=panand@redhat.com \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.