linux-kernel - Re: x86 embedded - Problem getting past 'move compressed kernel before decompression'

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]

Message-ID: <4B8C184E.2000400@gmail.com>
Date:	Tue, 02 Mar 2010 06:41:02 +1100
From:	Graeme Russ <graeme.russ@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: x86 embedded - Problem getting past 'move compressed kernel 
 before decompression'

H. Peter Anvin wrote:
> On 03/01/2010 03:56 AM, Graeme Russ wrote:
>> I have done a little more digging. By adding an ascii string before
>> relocated: label, I am able to determine that the int3 after the relocated:
>> label exists in bzImage at offset 0x1C3FD7
>>
>> EAX holds (for the jump) 0x5379d0 (different bzImage of course). The
>> contents of memory at this address is in bzImage at offset 0x1C09D7 - A
>> difference of 0x3600 (seems too even to be random)
>>
>> I'm obviously doing something hideously wrong, but what?
>>
> 
> 0x3600 sounds like the size of the real-mode code in bzImage.
> 

But what could I be doing to cause the miscalculation? From what I
understand, everything looks to be calculated at build time

Graeme
--
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/