| 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: Tue, 01 Jul 2008 19:50:14 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Mike Travis <travis@....com> Cc: "H. Peter Anvin" <hpa@...or.com>, Jeremy Fitzhardinge <jeremy@...p.org>, Christoph Lameter <cl@...ux-foundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>, Andrew Morton <akpm@...ux-foundation.org>, Jack Steiner <steiner@....com> Subject: Re: [crash, bisected] Re: [PATCH 3/4] x86_64: Fold pda into per cpu area Mike Travis <travis@....com> writes: > Ouch. How far into it do we need to investigate? I can surely compare the > vmlinux object files, but I'm not cognizant enough about the linker internals > to examine much more than that. As a first step we just need to know what we tell gcc or the linker to do, and what is incorrectly output. Once the problem is understood we can think about how to deal with the problem. What we really need is a recipe for success. A recipe for failure. At that point it should be much easier for someone else to reproduce the problem, and/or look into the specific details and see what is wrong or to suggest patches. The kernel is a significant enough program and a different enough one it is hard to predict how things go. Eric -- 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/
Powered by blists - more mailing lists