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
| ||
|
Date: Fri, 25 Aug 2017 10:01:58 -0500 From: Josh Poimboeuf <jpoimboe@...hat.com> To: Jiri Slaby <jslaby@...e.cz> Cc: "x86@...nel.org" <x86@...nel.org>, Linux kernel mailing list <linux-kernel@...r.kernel.org> Subject: Re: WARNING: at arch/x86/kernel/stacktrace.c:132 save_stack_trace_tsk_reliable On Fri, Aug 25, 2017 at 03:54:12PM +0200, Jiri Slaby wrote: > So now, there are two things: > 1) how to fix orc_find & unwind_init properly? > 2) how to generate an EMPTY hint for secondary_startup_64 and maybe > later REGS hint after the rsp setup there? The function seems to be a > pretty killer for orc generate (among others in head_64.S): I think the solution is to get head_64.S annotated properly. Then there won't be a gap between _stext and the first ORC entry, and we won't need to fix __orc_find(). I can work up a patch for you to test with. -- Josh
Powered by blists - more mailing lists