linux-kernel - BUG: unable to handle kernel NULL pointer dereference with dracut generated initrd

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20130322225513.GA4419@RD-HC.apollo.lv>
Date:	Sat, 23 Mar 2013 00:55:13 +0200
From:	Reinis Danne <rei4dan@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: BUG: unable to handle kernel NULL pointer dereference with dracut
 generated initrd

Hi!

I'm trying to generate initramfs using dracut, but the resulting
setup usually leads to hard hang of the system (or just doesnt
find HD and aborts) and in the rare cases where it does survive
the boot it reports BUGs in syslog.

I'm using Gentoo and until now I have compiled kernels and
generated initramfs using genkernel utility and those seem to
work. Maybe unrelated, but with v3.8 I have experienced system
lockup twice, both times after it was under a bit of load.

The hangs with dracut generated initramfs seem to be reproducible at least
since v3.7.10 and I have seen the BUG messages with v3.8 and even
v3.9-rc3-244-g9217cbb.


Mar 22 23:09:48 kernel: BUG: unable to handle kernel NULL pointer dereference at           (null)
Mar 22 23:09:48 kernel: IP: [<ffffffff8106325d>] futex_wake+0x69/0xfe
Mar 22 23:09:48 kernel: PGD 23d6c0067 PUD 235888067 PMD 0 
Mar 22 23:09:48 kernel: Oops: 0000 [#1] PREEMPT SMP 
Mar 22 23:09:48 kernel: Modules linked in:
Mar 22 23:09:48 kernel: CPU 7 
Mar 22 23:09:48 kernel: Pid: 401, comm: udevadm Not tainted 3.9.0-rc3+ #1 Dell Inc.          Dell System XPS L502X/0NJT03
Mar 22 23:09:48 kernel: RIP: 0010:[<ffffffff8106325d>]  [<ffffffff8106325d>] futex_wake+0x69/0xfe
Mar 22 23:09:48 kernel: RSP: 0018:ffff8802330efda8  EFLAGS: 00010246
Mar 22 23:09:48 kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000001567eda8
Mar 22 23:09:48 kernel: RDX: 0000000000000000 RSI: 00000000d3d3b172 RDI: ffffffffffffffe8
Mar 22 23:09:48 kernel: RBP: ffff8802330efe08 R08: 0000000049079e59 R09: 0000000000000000
Mar 22 23:09:48 kernel: R10: 000000000000000c R11: 0000000000000202 R12: 00000000ffffffff
Mar 22 23:09:48 kernel: R13: 0000000000000001 R14: ffffffff817c09e8 R15: ffffffff817c09e0
Mar 22 23:09:48 kernel: FS:  00007f689af00800(0000) GS:ffff88023e5c0000(0000) knlGS:0000000000000000
Mar 22 23:09:48 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 22 23:09:48 kernel: CR2: 0000000000000000 CR3: 000000023d6cd000 CR4: 00000000000407e0
Mar 22 23:09:48 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar 22 23:09:48 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Mar 22 23:09:48 kernel: Process udevadm (pid: 401, threadinfo ffff8802330ee000, task ffff88023d7c0040)
Mar 22 23:09:48 kernel: Stack:
Mar 22 23:09:48 kernel: ffff880233139ef8 00000001330f1a80 0000000000000029 00007fff6b583000
Mar 22 23:09:48 kernel: ffff8802330f1a80 0000000000000048 00000001330efea8 0000000000000081
Mar 22 23:09:48 kernel: 0000000000000046 0000000000000001 0000003000223100 000000009af00800
Mar 22 23:09:48 kernel: Call Trace:
Mar 22 23:09:48 kernel: [<ffffffff8106456b>] do_futex+0xde/0x8c1
Mar 22 23:09:48 kernel: [<ffffffff810266b2>] ? __do_page_fault+0x336/0x3da
Mar 22 23:09:48 kernel: [<ffffffff810e1889>] ? mntput+0x28/0x2a
Mar 22 23:09:48 kernel: [<ffffffff810ca9c5>] ? __fput+0x1b9/0x1d9
Mar 22 23:09:48 kernel: [<ffffffff81064e68>] sys_futex+0x11a/0x14e
Mar 22 23:09:48 kernel: [<ffffffff8102677e>] ? do_page_fault+0x9/0xb
Mar 22 23:09:48 kernel: [<ffffffff814b2292>] system_call_fastpath+0x16/0x1b
Mar 22 23:09:48 kernel: Code: ff 85 c0 89 c3 0f 85 a4 00 00 00 48 8d 7d b8 e8 d2 f0 ff ff 49 89 c7 48 89 c7 e8 30 e3 44 00 49 8b 47 08 4d 8d 77 08 48 8d 78 e8 <48> 8b 00 4c 8d 68 e8 eb 48 48 83 ff c8 74 37 48 8b 45 b8 48 39 
Mar 22 23:09:48 kernel: RIP  [<ffffffff8106325d>] futex_wake+0x69/0xfe
Mar 22 23:09:48 kernel: RSP <ffff8802330efda8>
Mar 22 23:09:48 kernel: CR2: 0000000000000000
Mar 22 23:09:48 kernel: ---[ end trace d0f4c3e979eb4d34 ]---


The kernel was compiled using genkernel and initramfs was generated using the
following command:
~# dracut -f -a "base caps debug i18n plymouth rootfs-block" --add-drivers "$(lsmod | awk '{print $1}')" foobar.img '3.9.0-rc3+'
~# mv foobar.img /boot/initramfs-dracut-x86_64-3.9.0-rc3+

In grub2 menu I pointed initrd to this dracut generated image. Also it seems
that it requires to blacklist nouveau to have any chance for successful boot
(rd.driver.blacklist=nouveau). This is an Optimus laptop with i7
SNB CPU and GeForce GT 540M GPU.

Config and more of the log (there are several traces in every
boot) in attachments. I have no idea what to do with this
further, any pointers are welcome.


Reinis

View attachment "config-v3.9-rc3-244-g9217cbb" of type "text/plain" (97499 bytes)

View attachment "syslog-v3.9-rc3-244-g9217cbb" of type "text/plain" (133048 bytes)