linux-kernel - [BUG?] recursive locking in acpi_bus_register

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]

Date:	Fri, 5 Feb 2010 15:58:07 +0900
From:	Minchan Kim <minchan.kim@...il.com>
To:	Len Brown <lenb@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	inux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [BUG?] recursive locking in acpi_bus_register_driver

Is this a known bug or my hardware is bad ?
I use mmotm 2010-02-03-20-09.

I didn't have a problem in 2.6.32.
Unfortunately I can't test it at next week.
I hope this problem can be reproduced easily.

I know gmail webserver would magle my text.
So I will attach my dmesg, config and cpuinfo.

---
...
...
PCI: Using MMCONFIG for extended config space
ACPI: No dock devices found.

=============================================
[ INFO: possible recursive locking detected ]
2.6.33-rc6-mm1+ #6
---------------------------------------------
swapper/1 is trying to acquire lock:
 (&dev->mutex){+.+...}, at: [<c03d57a4>] __driver_attach+0x54/0xa0

but task is already holding lock:
 (&dev->mutex){+.+...}, at: [<c03d5798>] __driver_attach+0x48/0xa0

other info that might help us debug this:
1 lock held by swapper/1:
 #0:  (&dev->mutex){+.+...}, at: [<c03d5798>] __driver_attach+0x48/0xa0

stack backtrace:
Pid: 1, comm: swapper Not tainted 2.6.33-rc6-mm1+ #6
Call Trace:
 [<c05b2022>] ? printk+0x18/0x1e
 [<c01762df>] __lock_acquire+0xfef/0x1240
 [<c01755d2>] ? __lock_acquire+0x2e2/0x1240
 [<c01765f5>] lock_acquire+0xc5/0xe0
 [<c03d57a4>] ? __driver_attach+0x54/0xa0
 [<c05b3552>] mutex_lock_nested+0x62/0x330
 [<c03d57a4>] ? __driver_attach+0x54/0xa0
 [<c03d57a4>] ? __driver_attach+0x54/0xa0
 [<c03d57a4>] __driver_attach+0x54/0xa0
 [<c03d4c5b>] bus_for_each_dev+0x5b/0x80
 [<c0378074>] ? acpi_device_remove+0x0/0x90
 [<c03d5329>] driver_attach+0x19/0x20
 [<c03d5750>] ? __driver_attach+0x0/0xa0
 [<c03d44c7>] bus_add_driver+0x1f7/0x310
 [<c0378074>] ? acpi_device_remove+0x0/0x90
 [<c03d5a75>] driver_register+0x75/0x160
 [<c083f493>] ? dock_init+0x0/0x81
 [<c083f514>] ? acpi_pci_root_init+0x0/0x25
 [<c037948c>] acpi_bus_register_driver+0x3a/0x3e
 [<c083f52a>] acpi_pci_root_init+0x16/0x25
 [<c0101123>] do_one_initcall+0x23/0x190
 [<c01a3bd7>] ? init_irq_proc+0x67/0x80
 [<c0815375>] kernel_init+0x150/0x1a9
 [<c0815225>] ? kernel_init+0x0/0x1a9
 [<c01033ba>] kernel_thread_helper+0x6/0x1c
ACPI Error (dsfield-0143): [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS
ACPI Error (psparse-0537): Method parse/execution failed
[\_SB_.PCI0._OSC] (Node f70194e0), AE_ALREADY_EXISTS
ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci_root PNP0A03:00: ignoring host bridge windows from ACPI; boot with
"pci=use_crs" to use them
pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cf7] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000d0000-0x000d3fff] (ignored)

---



-- 
Kind regards,
Minchan Kim

View attachment "dmesg.log" of type "text/x-log" (40754 bytes)

View attachment "cpuinfo.log" of type "text/x-log" (3204 bytes)

View attachment "config.log" of type "text/x-log" (81836 bytes)