linux-kernel - Re: [PATCH] s390:ftrace: add save_stack_trace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160129085936.09458371@gandalf.local.home>
Date:	Fri, 29 Jan 2016 08:59:36 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
Cc:	Pratyush Anand <panand@...hat.com>, schwidefsky@...ibm.com,
	linux-s390@...r.kernel.org, Chunyu Hu <chuhu@...hat.com>,
	open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] s390:ftrace: add save_stack_trace_regs()

On Fri, 29 Jan 2016 13:57:49 +0100
Heiko Carstens <heiko.carstens@...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.

-- Steve