Re: [Fastboot] [CFT] ELF Relocatable x86 and x86_64 bzImages
From: Eric W. Biederman
Date: Mon Aug 14 2006 - 17:15:18 EST
Vivek Goyal <vgoyal@xxxxxxxxxx> writes:
> On Mon, Aug 14, 2006 at 02:10:51PM -0600, Eric W. Biederman wrote:
>> "H. Peter Anvin" <hpa@xxxxxxxxx> writes:
>> > Vivek Goyal wrote:
>> >>> What about once the kernel is booted?
>> >> Sorry did not understand the question. Few more lines will help.
>> > Is this field intended to protect any kind of memory during the early boot
>> > of the kernel proper, or only the decompressor?
>> Yes, the field should account for memory usage until the kernel starts
>> doing the accounting at run time.
>> I'm actually surprised that taking into account the .bss was not enough to
>> cover up anything the decompressor was doing. Usually the kernel's .bss
>> is more than the extra 32K or so that the decompressor uses.
> I think .bss section size will act as a buffer for decompressor only if
> .bss is not part of compressed data hence decompressor does not have to
> move beyond bss and it can run very well from kernel bss space.
> But somehow on my machine, it looks like that bss is very much part
> of raw binary image hence part of compressed data (vmlinux.bin.gz).
> memsz exported in bzImage is same as size of raw output binary.
> Probably that's the reason that we are stomping other segments in my
> case and if my understanding is right then it should happen irrespective
> of kernel bss size.
> Here I am pasting how kernel vmlinux file program headers look like.
> .bss is mapped by first program header along with .text.
Ok. So somehow we have done the insane thing of putting .bss in the middle of
the executable. It might even be sane if it is just the .init sections we put
after it, but no we are putting .data after the .bss.
Well that easily explains why we had a problem.
Getting the proper accounting in for handling this case is probably reasonable.
It probably also makes sense for someone to take a good hard look at the crazy
ordering of sections on x86_64.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/