Re: [gentoo-hardened] 2.6.28-hardened-r7 hangs before starting /sbin/init

[Alex Efros]

Hi!

On Fri, Apr 03, 2009 at 08:50:37AM +0200, pageexec@××××××××.hu wrote:
> ok, can you add a printk into mm/mmap.c:mmap_region and print out all the
> arguments? that will show us at least what the kernel intended to mmap
> during execve. something like:
>
> printk("f:%p a:%0lx l:%0lx f:%0lx v:%0lx p:%0lx\n", file, addr, len, flags, vm_flags, pgoff);

Booting init=/bin/bash (PaX flags: -------x-e--)

Freeing unused kernel memory: 2024k freed
f:f6ce0c80 a:12b4d000 l:cb000 f:1812 v:1855 p:0
f:f6ce0c80 a:12c18000 l:7000 f:1812 v:1833 p:cb
f:f756b980 a:54720000 l:1c000 f:802 v:855 p:0
f:f756b980 a:5473a000 l:2000 f:812 v:833 p:1a
(hang)

... once again:

Freeing unused kernel memory: 2024k freed
f:f7655b00 a:1454e000 l:cb000 f:1812 v:1855 p:0
f:f7655b00 a:14619000 l:7000 f:1812 v:1833 p:cb
f:f76558c0 a:4de0a000 l:1c000 f:802 v:855 p:0
f:f76558c0 a:4de24000 l:2000 f:812 v:833 p:1a
(hang)

Booting init=/bin/bash-m (PaX flags: -----m-x-e--)

Freeing unused kernel memory: 2024k freed
f:f74f52c0 a:126a3000 l:cb000 f:1812 v:1875 p:0
f:f74f52c0 a:1276e000 l:7000 f:1812 v:1873 p:cb
f:f749a6c0 a:524ad000 l:1c000 f:802 v:875 p:0
f:f749a6c0 a:524c7000 l:2000 f:812 v:873 p:1a
f:f7577800 a:524a6000 l:6000 f:2 v:71 p:0
f:00000000 a:524a5000 l:1000 f:22 v:73 p:524a5
f:f749a600 a:5245a000 l:4b000 f:2 v:75 p:0
f:f749a600 a:5249c000 l:9000 f:12 v:73 p:42
f:f74f5440 a:52456000 l:4000 f:2 v:75 p:0
f:f74f5440 a:52458000 l:2000 f:12 v:73 p:1
f:f752ebc0 a:5231b000 l:13b000 f:2 v:75 p:0
f:f752ebc0 a:52450000 l:3000 f:12 v:73 p:135
f:00000000 a:52453000 l:3000 f:32 v:73 p:52453
f:00000000 a:5231a000 l:1000 f:22 v:73 p:5231a
f:00000000 a:524ab000 l:1000 f:22 v:73 p:524ab
f:f749a540 a:524a6000 l:6000 f:2 v:71 p:0
f:f752eb00 a:52311000 l:9000 f:2 v:75 p:0
f:f752eb00 a:52318000 l:2000 f:12 v:73 p:6
f:f7577800 a:522fa000 l:17000 f:2 v:75 p:0
f:f7577800 a:5230d000 l:2000 f:12 v:73 p:12
f:00000000 a:5230f000 l:2000 f:32 v:73 p:5230f
f:f752ea40 a:524a6000 l:6000 f:2 v:71 p:0
f:f752e980 a:522f0000 l:a000 f:2 v:75 p:0
f:f752e980 a:522f8000 l:2000 f:12 v:73 p:7
f:f75778c0 a:522e5000 l:b000 f:2 v:75 p:0
f:f75778c0 a:522ee000 l:2000 f:12 v:73 p:8
f:f749a540 a:524aa000 l:2000 f:1 v:d1 p:0
f:00000000 a:524ab000 l:1000 f:22 v:73 p:524ab
f:f74f5380 a:1519d000 l:9000 f:1812 v:1855 p:0
f:f74f5380 a:151a6000 l:2000 f:1812 v:1833 p:8
f:f752e8c0 a:55575000 l:1c000 f:802 v:855 p:0
f:f752e8c0 a:5558f000 l:2000 f:812 v:833 p:1a
f:f752ea40 a:5556e000 l:6000 f:2 v:31 p:0
f:00000000 a:5556d000 l:1000 f:22 v:33 p:5556d
f:f7577980 a:55432000 l:13b000 f:2 v:55 p:0
f:f7577980 a:55567000 l:3000 f:12 v:33 p:135
f:00000000 a:5556a000 l:3000 f:32 v:33 p:5556a
f:00000000 a:55431000 l:1000 f:22 v:33 p:55431
f:00000000 a:55573000 l:1000 f:22 v:33 p:55573
f:00000000 a:55573000 l:1000 f:22 v:33 p:55573
f:00000000 a:524aa000 l:1000 f:22 v:73 p:524aa
(none) / #

> also to simplify matters, can you just run with the PaX test patch alone?

which exactly version of kernel and PaX patch I should test?

-- 
			WBR, Alex.