linux-kernel - Re: Crash of 3.12-rc2 BUG: unable to handle kernel NULL pointer dereference

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]

Date:	Fri, 27 Sep 2013 10:04:44 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Zdenek Kabelac <zkabelac@...hat.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Russell King <linux@....linux.org.uk>
Subject: Re: Crash of 3.12-rc2 BUG: unable to handle kernel NULL pointer dereference

[+cc Thomas, Russell]

On Fri, Sep 27, 2013 at 7:13 AM, Zdenek Kabelac <zkabelac@...hat.com> wrote:
> Dne 27.9.2013 13:57, Zdenek Kabelac napsal(a):
>
>> Hi
>>
>>
>> I'm trying to use -rc2 kernel however I'm getting quite often regular
>> kernel
>> panic:
>>
>> Here is a BUG trace from kvm running this kernel:
>> (I'm building kernel with some kernel debug checks)
>> (Kernel is used in 64bit qemu and running 32bit Debian environment)
>> linux-vanilla git: 4b97280675f45c1650ee4e388bd711ecbb18c4b4
>> (on top of that there are few minor unrelated patches)
>>
>>
>> [  235.631952] loop: module loaded
>> [  235.971853] bio: create slab <bio-1> at 1
>> [  237.355014] bio: create slab <bio-2> at 2
>> [  237.671371] BUG: unable to handle kernel NULL pointer dereference at
>> 0000000000000018
>> [  237.674537] IP: [<ffffffff8105a008>]
>> get_next_timer_interrupt+0x168/0x250
>> [  237.674537] PGD 16939067 PUD 14257067 PMD 0
>> [  237.674537] Oops: 0000 [#1] PREEMPT SMP
>> [  237.674537] Modules linked in: loop dm_thin_pool dm_persistent_data
>
>
>
> Here is the same trace from my native  HW   Lenovo T61:
>
> I'm suspecting new debug option:
>  CONFIG_DEBUG_KOBJECT_RELEASE which I've recently enabled)
>
> I've also noticed there are much older reports for this problem:
> i.e. https://lkml.org/lkml/2013/3/9/3
>
> I can trigger this bug very easily (makes 3.12-rc2 unusable for my desktop)

Yep, I see this crash 100% of the time with v3.12-rc2 and
CONFIG_DEBUG_KOBJECT_RELEASE=y with this qemu invocation and attached
q35-chipset.cfg:

/usr/local/bin/qemu-system-x86_64 -M q35 -readconfig ./q35-chipset.cfg
-enable-kvm -m 512 -drive file=ubuntu.img,if=none,id=mydisk -device
ide-drive,drive=mydisk,bus=ide.0 -nographic -monitor
telnet:localhost:7001,server,nowait,nodelay -kernel
~/linux/arch/x86/boot/bzImage -append "console=ttyS0,115200n8
root=/dev/sda1 ignore_loglevel printk.time=n"

Download attachment "q35-chipset.cfg" of type "application/octet-stream" (2909 bytes)