linux-kernel - Re: CONFIG_NO_BOOTMEM woes, 2.6.34-rc1

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: <4BA0AAC8.5000702@redhat.com>
Date:	Wed, 17 Mar 2010 12:11:20 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: CONFIG_NO_BOOTMEM woes, 2.6.34-rc1

On 03/15/2010 07:52 PM, Yinghai Lu wrote:
> On 03/15/2010 08:28 AM, Avi Kivity wrote:
>    
>> With CONFIG_NO_BOOTMEM=y, I get:
>>
>> kobject '' (c252bfdc): tried to add an uninitialized object, something
>> is seriously wrong.
>> Pid: 1, comm: swapper Not tainted 2.6.34-rc1 #121
>> Call Trace:
>>   [<c07803f5>] ? printk+0x14/0x17
>>   [<c05a4cea>] kobject_add+0x28/0x49
>>   [<c06e65c1>] add_sysfs_fw_map_entry+0x5b/0x74
>>   [<c09fa56f>] memmap_init+0x13/0x2d
>>   [<c040305b>] do_one_initcall+0x51/0x13f
>>   [<c09ca376>] kernel_init+0x122/0x1a3
>>   [<c09ca254>] ? kernel_init+0x0/0x1a3
>>   [<c0408ffe>] kernel_thread_helper+0x6/0x10
>> ------------[ cut here ]------------
>> WARNING: at lib/kobject.c:595 kobject_put+0x27/0x3c()
>>
>> a bit after which the kernel dies.  Inspection of memmap_init() and
>> related code appears to call kobject_init() correctly.
>>
>> With CONFIG_NO_BOOTMEM, the kernel hangs in early boot before displaying
>> anything.
>>
>> 2.6.34-rc1, i386 (x86_64 works fine).
>>
>>      
> can you send out
> .config and boot log for old kernel ...
>
>    

I reproduced this on x86_64 as well (both physical and virtual), fails 
earlier this time.

Stack trace:
#0  ?? () at arch/x86/kernel/head_64.S:318
#1  0xffffffff812039dd in strnlen (s=0x1 <Address 0x1 out of bounds>, 
count=<value optimized out>) at lib/string.c:403
#2  0xffffffff81204fdf in string (buf=0xffffffff817ff5b0 "(null): 9f3ff 
ffffffff81531e70  ", '0' <repeats 14 times>, "3f\n",
     end=0xffffffff817ff9b0 "", s=0x9f400 <Address 0x9f400 out of 
bounds>, spec=<value optimized out>) at lib/vsprintf.c:546
#3  0xffffffff81205ea2 in vsnprintf (buf=0xffffffff817ff5b0 "(null): 
9f3ff ffffffff81531e70  ", '0' <repeats 14 times>, "3f\n", size=1024,
     fmt=0xffffffff81591c1e ": %llx %llx %s %p\n", 
args=0xffffffff815ddda8) at lib/vsprintf.c:1316
#4  0xffffffff812061e8 in vscnprintf (buf=<value optimized out>, 
size=1024, fmt=<value optimized out>, args=<value optimized out>)
     at lib/vsprintf.c:1427
#5  0xffffffff81046445 in vprintk (fmt=0xffffffff81591c1c "%s: %llx %llx 
%s %p\n", args=0xffffffff815ddda8) at kernel/printk.c:709
#6  0xffffffff813cecb0 in printk (fmt=<value optimized out>) at 
kernel/printk.c:590
#7  0xffffffff81329ebb in firmware_map_add_entry (start=652288, 
end=655359, type=0xffffffff81530231 "reserved", entry=0xffff88000190e8c0)
     at drivers/firmware/memmap.c:114
#8  0xffffffff81752711 in firmware_map_add_early (start=652288, 
end=655359, type=0xffffffff81530231 "reserved") at 
drivers/firmware/memmap.c:197
#9  0xffffffff8172776c in e820_reserve_resources () at 
arch/x86/kernel/e820.c:1090
#10 0xffffffff81726c5a in ?? ()
#11 0xffffffff81723a2a in start_kernel () at init/main.c:562
#12 0xffffffff817232a0 in x86_64_start_reservations 
(real_mode_data=<value optimized out>) at arch/x86/kernel/head64.c:121
#13 0xffffffff8172339c in x86_64_start_kernel (real_mode_data=0x13610 
<Address 0x13610 out of bounds>) at arch/x86/kernel/head64.c:94
#14 0x0000000000000000 in ?? ()

No dmesg.

.config attached.




-- 
error compiling committee.c: too many arguments to function


View attachment ".config" of type "text/plain" (47407 bytes)