====================================================== [ INFO: possible circular locking dependency detected ] 4.9.123-g8dd3fc2 #27 Not tainted ------------------------------------------------------- syz-executor5/11939 is trying to acquire lock: (rtnl_mutex){+.+.+.}, at: [] rtnl_lock+0x17/0x20 net/core/rtnetlink.c:70 but task is already holding lock: (sk_lock-AF_INET){+.+.+.}, at: [] lock_sock include/net/sock.h:1404 [inline] (sk_lock-AF_INET){+.+.+.}, at: [] do_ip_setsockopt.isra.14+0x269/0x2b10 net/ipv4/ip_sockglue.c:639 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: lock_acquire+0x130/0x3e0 kernel/locking/lockdep.c:3756 lock_sock_nested+0xc6/0x120 net/core/sock.c:2511 lock_sock include/net/sock.h:1404 [inline] do_ip_setsockopt.isra.14+0x12a/0x2b10 net/ipv4/ip_sockglue.c:639 ip_setsockopt+0x3a/0xb0 net/ipv4/ip_sockglue.c:1243 tcp_setsockopt+0x88/0xe0 net/ipv4/tcp.c:2758 sock_common_setsockopt+0x9a/0xe0 net/core/sock.c:2706 SYSC_setsockopt net/socket.c:1773 [inline] SyS_setsockopt+0x166/0x260 net/socket.c:1752 do_syscall_64+0x1a6/0x490 arch/x86/entry/common.c:282 entry_SYSCALL_64_after_swapgs+0x5d/0xdb check_prev_add kernel/locking/lockdep.c:1828 [inline] check_prevs_add kernel/locking/lockdep.c:1938 [inline] validate_chain kernel/locking/lockdep.c:2265 [inline] __lock_acquire+0x3019/0x4070 kernel/locking/lockdep.c:3345 lock_acquire+0x130/0x3e0 kernel/locking/lockdep.c:3756 __mutex_lock_common kernel/locking/mutex.c:521 [inline] mutex_lock_nested+0xc0/0x870 kernel/locking/mutex.c:621 rtnl_lock+0x17/0x20 net/core/rtnetlink.c:70 mrtsock_destruct+0x3b/0x1e0 net/ipv4/ipmr.c:1231 ip_ra_control+0x2c2/0x420 net/ipv4/ip_sockglue.c:363 do_ip_setsockopt.isra.14+0x15ff/0x2b10 net/ipv4/ip_sockglue.c:1140 ip_setsockopt+0x3a/0xb0 net/ipv4/ip_sockglue.c:1243 raw_setsockopt+0xb7/0xd0 net/ipv4/raw.c:833 sock_common_setsockopt+0x9a/0xe0 net/core/sock.c:2706 SYSC_setsockopt net/socket.c:1773 [inline] SyS_setsockopt+0x166/0x260 net/socket.c:1752 do_syscall_64+0x1a6/0x490 arch/x86/entry/common.c:282 entry_SYSCALL_64_after_swapgs+0x5d/0xdb other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sk_lock-AF_INET); lock(rtnl_mutex); lock(sk_lock-AF_INET); lock(rtnl_mutex); *** DEADLOCK *** 1 lock held by syz-executor5/11939: #0: (sk_lock-AF_INET){+.+.+.}, at: [] lock_sock include/net/sock.h:1404 [inline] #0: (sk_lock-AF_INET){+.+.+.}, at: [] do_ip_setsockopt.isra.14+0x269/0x2b10 net/ipv4/ip_sockglue.c:639 stack backtrace: CPU: 1 PID: 11939 Comm: syz-executor5 Not tainted 4.9.123-g8dd3fc2 #27 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 ffff8801a6a8f5f8 ffffffff81eb9689 ffffffff8559eeb0 ffffffff855e9b20 ffffffff8559eeb0 ffff88019ba808e8 ffff88019ba80000 ffff8801a6a8f640 ffffffff81428925 0000000000000001 000000009ba80000 0000000000000001 Call Trace: [] __dump_stack lib/dump_stack.c:15 [inline] [] dump_stack+0xc1/0x128 lib/dump_stack.c:51 [] print_circular_bug.cold.51+0x1bd/0x27d kernel/locking/lockdep.c:1202 [] check_prev_add kernel/locking/lockdep.c:1828 [inline] [] check_prevs_add kernel/locking/lockdep.c:1938 [inline] [] validate_chain kernel/locking/lockdep.c:2265 [inline] [] __lock_acquire+0x3019/0x4070 kernel/locking/lockdep.c:3345 [] lock_acquire+0x130/0x3e0 kernel/locking/lockdep.c:3756 [] __mutex_lock_common kernel/locking/mutex.c:521 [inline] [] mutex_lock_nested+0xc0/0x870 kernel/locking/mutex.c:621 [] rtnl_lock+0x17/0x20 net/core/rtnetlink.c:70 [] mrtsock_destruct+0x3b/0x1e0 net/ipv4/ipmr.c:1231 [] ip_ra_control+0x2c2/0x420 net/ipv4/ip_sockglue.c:363 [] do_ip_setsockopt.isra.14+0x15ff/0x2b10 net/ipv4/ip_sockglue.c:1140 [] ip_setsockopt+0x3a/0xb0 net/ipv4/ip_sockglue.c:1243 [] raw_setsockopt+0xb7/0xd0 net/ipv4/raw.c:833 [] sock_common_setsockopt+0x9a/0xe0 net/core/sock.c:2706 [] SYSC_setsockopt net/socket.c:1773 [inline] [] SyS_setsockopt+0x166/0x260 net/socket.c:1752 [] do_syscall_64+0x1a6/0x490 arch/x86/entry/common.c:282 [] entry_SYSCALL_64_after_swapgs+0x5d/0xdb FAT-fs (loop3): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop6): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1) FAT-fs (loop0): Invalid FSINFO signature: 0x00000000, 0x00000000 (sector = 1)