linux-kernel - Re: [PATCH v4 1/6] arm64: ftrace: adjust callsite addresses examined by stack tracer

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 2 Nov 2015 13:20:43 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Will Deacon <will.deacon@....com>
Cc:	AKASHI Takahiro <takahiro.akashi@...aro.org>,
	catalin.marinas@....com, jungseoklee85@...il.com, olof@...om.net,
	broonie@...nel.org, david.griego@...aro.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 1/6] arm64: ftrace: adjust callsite addresses
 examined by stack tracer

On Fri, 30 Oct 2015 11:16:19 +0000
Will Deacon <will.deacon@....com> wrote:

> On Fri, Oct 30, 2015 at 02:25:36PM +0900, AKASHI Takahiro wrote:
> > On arm64, no PC values returned by save_stack_trace() will match to LR
> > values saved in stack frames on a stack after the following commit:
> >     commit e306dfd06fcb ("ARM64: unwind: Fix PC calculation")
> > As a result, the output from stack tracer will be messed up.
> 
> FWIW, we've decided to revert that patch for the moment. We're the only
> architecture making that kind of adjustment, so we should fix that before
> building on top of it.
> 
>

What is the status of this patch set. I'm currently pulling in last
minute patches for 4.3 and should the ftrace patch in this series be
applied? (I still need to review it too).

-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/