linux-kernel - 2.6.31-rc3: lockdep warning triggered by dup

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>] [day] [month] [year] [list]

Message-ID: <e2e108260908230036x6e0bfa63y66675c55131a8008@mail.gmail.com>
Date:	Sun, 23 Aug 2009 09:36:10 +0200
From:	Bart Van Assche <bart.vanassche@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Roland Dreier <rdreier@...co.com>
Subject: 2.6.31-rc3: lockdep warning triggered by dup_fd

Hello,

The backtrace below has been observed once with a kernel compiled from
an unmodified infiniband git tree
(http://git.kernel.org/?p=linux/kernel/git/roland/infiniband.git). Has
anyone observed similar behavior before ? Is this a known issue that
has already been fixed in a more recent release candidate of the
2.6.31 kernel ?

Bart.

------------[ cut here ]------------
WARNING: at kernel/lockdep.c:732 register_lock_class+0x149/0x450()
Hardware name: P5Q DELUXE
Modules linked in: af_packet cpufreq_conservative cpufreq_userspace
cpufreq_powersave acpi_cpufreq fuse md_mod dm_mod coretemp hwmon
8250_pnp 8250 pcspkr serial_core button mlx4_core sky2 sr_mod sg
sd_mod uhci_hcd ehci_hcd usbcore ext3 mbcache jbd fan ide_pci_generic
ide_core ata_generic ata_piix thermal processor pata_jmicron ahci
Pid: 2595, comm: ifup Tainted: G        W  2.6.31-rc3-default #1
Call Trace:
 [<ffffffff8106f939>] ? register_lock_class+0x149/0x450
 [<ffffffff81046cb8>] warn_slowpath_common+0x78/0xd0
 [<ffffffff81046d1f>] warn_slowpath_null+0xf/0x20
 [<ffffffff8106f939>] register_lock_class+0x149/0x450
 [<ffffffff81072c2a>] __lock_acquire+0x49a/0x1230
 [<ffffffff81071ea4>] ? debug_check_no_locks_freed+0x94/0x160
 [<ffffffff81071dad>] ? trace_hardirqs_on_caller+0x14d/0x1a0
 [<ffffffff81073a16>] lock_acquire+0x56/0x80
 [<ffffffff810ddc2d>] ? dup_fd+0xbd/0x380
 [<ffffffff81314ef1>] _spin_lock+0x31/0x70
 [<ffffffff810ddc2d>] ? dup_fd+0xbd/0x380
 [<ffffffff810ddc2d>] dup_fd+0xbd/0x380
 [<ffffffff8103a41c>] ? set_task_cpu+0x5c/0x210
 [<ffffffff81045746>] copy_process+0x956/0x13d0
 [<ffffffff81046247>] do_fork+0x87/0x3f0
 [<ffffffff810713b5>] ? lock_release_holdtime+0x35/0x1b0
 [<ffffffff81071dad>] ? trace_hardirqs_on_caller+0x14d/0x1a0
 [<ffffffff81071e0d>] ? trace_hardirqs_on+0xd/0x10
 [<ffffffff81314cab>] ? _spin_unlock_irq+0x2b/0x40
 [<ffffffff8100b4dc>] ? sysret_check+0x27/0x62
 [<ffffffff81009c03>] sys_clone+0x23/0x30
 [<ffffffff8100b813>] stub_clone+0x13/0x20
 [<ffffffff8100b4ab>] ? system_call_fastpath+0x16/0x1b
---[ end trace 7491f358a793e951 ]---
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/