Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754674AbYGAR1P (ORCPT ); Tue, 1 Jul 2008 13:27:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751664AbYGAR1A (ORCPT ); Tue, 1 Jul 2008 13:27:00 -0400 Received: from gw.goop.org ([64.81.55.164]:50463 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751331AbYGAR07 (ORCPT ); Tue, 1 Jul 2008 13:26:59 -0400 Message-ID: <486A68DD.80702@goop.org> Date: Tue, 01 Jul 2008 10:26:53 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: "H. Peter Anvin" CC: "Eric W. Biederman" , Mike Travis , Christoph Lameter , Linux Kernel Mailing List Subject: Re: [crash, bisected] Re: [PATCH 3/4] x86_64: Fold pda into per cpu area References: <20080604003018.538497000@polaris-admin.engr.sgi.com> <485AADAC.3070301@sgi.com> <485AB78B.5090904@goop.org> <485AC120.6010202@sgi.com> <485AC5D4.6040302@goop.org> <485ACA8F.10006@sgi.com> <485ACD92.8050109@sgi.com> <485AD138.4010404@goop.org> <485ADA12.5010505@sgi.com> <485ADC73.60009@goop.org> <485BDB04.4090709@sgi.com> <485BE80E.10209@goop.org> <485BF8F5.6010802@goop.org> <485BFFC5.6020404@sgi.com> <486912C4.8070705@sgi.com> <48691556.2080208@zytor.com> <48691E8B.4040605@sgi.com> <48694B3B.3010600@goop.org> <486A61A7.1000902@zytor.com> In-Reply-To: <486A61A7.1000902@zytor.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 991 Lines: 27 H. Peter Anvin wrote: > Eric W. Biederman wrote: >>> >>> The zero-based PDA mechanism requires the introduction of a new ELF >>> segment >>> based at vaddr 0 which is sufficiently unusual that it wouldn't >>> surprise me if >>> its triggering some toolchain bug. >> >> Agreed. Given the previous description my hunch is that the bug is >> occurring >> during objcopy. If vmlinux is good and the compressed kernel is bad. >> > > Actually, it's not all that unusual... it's pretty common in various > restricted environments. That being said, it's probably uncommon for > *64-bit* code. Well, it's also unusual because 1) it's vaddr 0, but paddr , and 2) the PHDRs are not sorted by vaddr order. 2) might actually be a bug. J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/