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
| ||
|
Message-ID: <20171212130246.GA4391@lst.de> Date: Tue, 12 Dec 2017 14:02:46 +0100 From: Torsten Duwe <duwe@....de> To: Miroslav Benes <mbenes@...e.cz> Cc: Michael Ellerman <mpe@...erman.id.au>, Jiri Kosina <jkosina@...e.cz>, Balbir Singh <bsingharora@...il.com>, linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, live-patching@...r.kernel.org Subject: Re: [PATCH] On ppc64le we HAVE_RELIABLE_STACKTRACE On Tue, Dec 12, 2017 at 01:12:37PM +0100, Miroslav Benes wrote: > > I think that this is not enough. You need to also implement > save_stack_trace_tsk_reliable() for powerpc defined as __weak in > kernel/stacktrace.c. See arch/x86/kernel/stacktrace.c for reference, but I > think it would be much much simpler here given the changelog description. Is there an exhaustive, definite, non-x86-centric description of the cases this function needs to look for? Maybe some sort of formal specification? Torsten
Powered by blists - more mailing lists