linux-kernel - [BUG #12515] 2.6.29-rc2-git1: possible circular locking #0: (sk_lock-AF_PACKET){--..}, at: [<c1279838>] sock

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: <49799691.3070701@ribosome.natur.cuni.cz>
Date:	Fri, 23 Jan 2009 11:06:09 +0100
From:	Martin MOKREJŠ <mmokrejs@...osome.natur.cuni.cz>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: [BUG #12515] 2.6.29-rc2-git1: possible circular locking #0: (sk_lock-AF_PACKET){--..},
 at: [<c1279838>] sock_setsockopt+0x12b/0x4a4

Hi,
  I haven't received any answer on this bug report so I am re-trying
over the email list. Running tcpdump under heavy load/io I got this
stacktrace. Snippet from dmesg output follows:


device eth0 entered promiscuous mode

=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.29-rc2-git1 #1
-------------------------------------------------------
tcpdump/3734 is trying to acquire lock:
 (&mm->mmap_sem){----}, at: [<c1053294>] might_fault+0x30/0x6b

but task is already holding lock:
 (sk_lock-AF_PACKET){--..}, at: [<c12798c8>] sock_setsockopt+0x12b/0x4a4

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (sk_lock-AF_PACKET){--..}:
       [<c1033a0d>] add_lock_to_list+0x5e/0x8b
       [<c10365ae>] __lock_acquire+0xfb8/0x12e5
       [<c12cc63c>] packet_mmap+0x2e/0xf4
       [<c12cc63c>] packet_mmap+0x2e/0xf4
       [<c1036922>] lock_acquire+0x47/0x5e
       [<c12cc63c>] packet_mmap+0x2e/0xf4
       [<c1278548>] lock_sock_nested+0xac/0xb9
       [<c12cc63c>] packet_mmap+0x2e/0xf4
       [<c12cc63c>] packet_mmap+0x2e/0xf4
       [<c1034e94>] trace_hardirqs_on_caller+0x104/0x124
       [<c12759fa>] sock_mmap+0xc/0xe
       [<c10588f9>] mmap_region+0x27e/0x4b4
       [<c1058d1e>] do_mmap_pgoff+0x1ef/0x239
       [<c10057cf>] sys_mmap2+0x58/0x76
       [<c1002cd5>] sysenter_do_call+0x12/0x35
       [<ffffffff>] 0xffffffff

-> #0 (&mm->mmap_sem){----}:
       [<c103507d>] print_circular_bug_entry+0x36/0x3d
       [<c10362d1>] __lock_acquire+0xcdb/0x12e5
       [<c1034cf3>] mark_held_locks+0x50/0x66
       [<c101ff01>] local_bh_enable+0x97/0x9a
       [<c1036922>] lock_acquire+0x47/0x5e
       [<c1053294>] might_fault+0x30/0x6b
       [<c10532b1>] might_fault+0x4d/0x6b
       [<c1053294>] might_fault+0x30/0x6b
       [<c1137907>] copy_from_user+0x27/0x10e
       [<c1279bcb>] sock_setsockopt+0x42e/0x4a4
       [<c10532b4>] might_fault+0x50/0x6b
       [<c127636a>] sys_setsockopt+0x4c/0x7d
       [<c1277957>] sys_socketcall+0x135/0x18c
       [<c1002cd5>] sysenter_do_call+0x12/0x35
       [<ffffffff>] 0xffffffff

other info that might help us debug this:

1 lock held by tcpdump/3734:
 #0:  (sk_lock-AF_PACKET){--..}, at: [<c12798c8>] sock_setsockopt+0x12b/0x4a4

stack backtrace:
Pid: 3734, comm: tcpdump Not tainted 2.6.29-rc2-git1 #1
Call Trace:
 [<c10352c1>] print_circular_bug_tail+0xa5/0xaf
 [<c103507d>] print_circular_bug_entry+0x36/0x3d
 [<c10362d1>] __lock_acquire+0xcdb/0x12e5
 [<c1034cf3>] mark_held_locks+0x50/0x66
 [<c101ff01>] local_bh_enable+0x97/0x9a
 [<c1036922>] lock_acquire+0x47/0x5e
 [<c1053294>] might_fault+0x30/0x6b
 [<c10532b1>] might_fault+0x4d/0x6b
 [<c1053294>] might_fault+0x30/0x6b
 [<c1137907>] copy_from_user+0x27/0x10e
 [<c1279bcb>] sock_setsockopt+0x42e/0x4a4
 [<c10532b4>] might_fault+0x50/0x6b
 [<c127636a>] sys_setsockopt+0x4c/0x7d
 [<c1277957>] sys_socketcall+0x135/0x18c
 [<c1002cd5>] sysenter_do_call+0x12/0x35
device eth0 left promiscuous mode


More details are at http://bugzilla.kernel.org/show_bug.cgi?id=12515
Please Cc: me in replies. Thanks.
Martin
--
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/