linux-kernel - kernel won't boot if kernel image passes 0xffffffff82000000

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-next>] [day] [month] [year] [list]

Message-ID: <AANLkTi=29x3ng4uhUAMewe5Gr25ayDknJS9iGS4c51Yw@mail.gmail.com>
Date:	Thu, 14 Oct 2010 16:58:51 -0700
From:	Rong Xu <rong.xu3@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: kernel won't boot if kernel image passes 0xffffffff82000000

I found that if the kernel image passes 0xffffffff82000000, the kernel won't
boot. It dies in very early stage of booting, right after the kernel image
is loaded.

More details:
This is 2.6.26 kernel on x86-64 platform, using the default x86_64 config.
I'm not booting with any option. Kernel image starts from
0xffffffff80000000. kernel_text starts from 0xffffffff80200000. From the
comments in head64.S, I suppose we can use 512M for kernel image, to
0xffffffffa000000 where the module starts. But my experiments shows the
maximum kernel image size is from 0xffffffff80200000 to 0xffffffff82000000
(30MB).

Here are some of the experiments I did:
(1) increase the bss size to let it pass 0xffffffff82000000, then kernel
    won't boot.
(2) change the linker-script to move the bss section of a good kernel,
     making part of the section pass 0xffffffff82000000, then the kernel
     becomes not bootable.
(3) change the linker-script to move the bss section of a good kernel, not
     letting it pass 0xffffffff82000000. the result kernel can boot.
(4) keep all sections intact and move PHYSICAL_START to make the end of
     kernel image pass 0xffffffff82000000. Kernel won't boot
(5) keep all sections intact and move PHYSICAL_START, not letting the kernel
     image pass 0xffffffff82000000. the result kernel can boot.

So it looks this not related to the kernel size, but to the address
0xffffffff82000000. what is special for this address? I could not find any
documentation (or source reference) to this address.
In the head_64.S, we actually initialized the PMD entries for all the
possible 512MB space. I think we should be able to use it. In a booted
kernel, the PMD entries for 0xffffffff82000000 is zeroed out (when I dump
the kernel page table). so I guess this address is not used by other part of
kernel.

I tried kernel 2.6.27 and it seems to have the same issue.

Any comment?

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