====================================================== [ INFO: possible circular locking dependency detected ] 4.9.109-ga4230be #48 Not tainted ------------------------------------------------------- syz-executor5/11468 is trying to acquire lock: (sk_lock-AF_INET[ 112.200297] FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem ){+.+.+.}, at: [] lock_sock include/net/sock.h:1404 [inline] ){+.+.+.}, at: [] do_ip_setsockopt.isra.13+0x12a/0x2b10 net/ipv4/ip_sockglue.c:636 but task is already holding lock: (rtnl_mutex){+.+.+.}, at: [] rtnl_lock+0x17/0x20 net/core/rtnetlink.c:70 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 __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:360 do_ip_setsockopt.isra.13+0x15ff/0x2b10 net/ipv4/ip_sockglue.c:1137 ip_setsockopt+0x3a/0xb0 net/ipv4/ip_sockglue.c:1240 raw_setsockopt+0xb7/0xd0 net/ipv4/raw.c:833 sock_common_setsockopt+0x9a/0xe0 net/core/sock.c:2706 SYSC_setsockopt net/socket.c:1772 [inline] SyS_setsockopt+0x166/0x260 net/socket.c:1751 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 lock_sock_nested+0xc6/0x120 net/core/sock.c:2511 lock_sock include/net/sock.h:1404 [inline] do_ip_setsockopt.isra.13+0x12a/0x2b10 net/ipv4/ip_sockglue.c:636 ip_setsockopt+0x3a/0xb0 net/ipv4/ip_sockglue.c:1240 udp_setsockopt+0x4a/0x90 net/ipv4/udp.c:2091 sock_common_setsockopt+0x9a/0xe0 net/core/sock.c:2706 SYSC_setsockopt net/socket.c:1772 [inline] SyS_setsockopt+0x166/0x260 net/socket.c:1751 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(rtnl_mutex); lock(sk_lock-AF_INET); lock(rtnl_mutex); lock(sk_lock-AF_INET); *** DEADLOCK *** 1 lock held by syz-executor5/11468: #0: (rtnl_mutex){+.+.+.}, at: [] rtnl_lock+0x17/0x20 net/core/rtnetlink.c:70 stack backtrace: CPU: 0 PID: 11468 Comm: syz-executor5 Not tainted 4.9.109-ga4230be #48 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 ffff88018ef77758 ffffffff81eb3e29 ffffffff855e79b0 ffffffff8559cef0 ffffffff855e79b0 ffff880181b220e8 ffff880181b21800 ffff88018ef777a0 ffffffff814262d4 0000000000000001 0000000081b21800 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 [] lock_sock_nested+0xc6/0x120 net/core/sock.c:2511 [] lock_sock include/net/sock.h:1404 [inline] [] do_ip_setsockopt.isra.13+0x12a/0x2b10 net/ipv4/ip_sockglue.c:636 [] ip_setsockopt+0x3a/0xb0 net/ipv4/ip_sockglue.c:1240 [] udp_setsockopt+0x4a/0x90 net/ipv4/udp.c:2091 [] sock_common_setsockopt+0x9a/0xe0 net/core/sock.c:2706 [] SYSC_setsockopt net/socket.c:1772 [inline] [] SyS_setsockopt+0x166/0x260 net/socket.c:1751 [] do_syscall_64+0x1a6/0x490 arch/x86/entry/common.c:282 [] entry_SYSCALL_64_after_swapgs+0x5d/0xdb FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem netlink: 4 bytes leftover after parsing attributes in process `syz-executor0'. netlink: 4 bytes leftover after parsing attributes in process `syz-executor0'. netlink: 4 bytes leftover after parsing attributes in process `syz-executor0'. EXT4-fs (sda1): Unrecognized mount option "noquota?" or missing value relay: one or more items not logged [item size (56) > sub-buffer size (9)] netlink: 4 bytes leftover after parsing attributes in process `syz-executor0'. FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem netlink: 4 bytes leftover after parsing attributes in process `syz-executor0'. netlink: 4 bytes leftover after parsing attributes in process `syz-executor0'. netlink: 4 bytes leftover after parsing attributes in process `syz-executor5'. EXT4-fs (sda1): Unrecognized mount option "noquota?" or missing value netlink: 4 bytes leftover after parsing attributes in process `syz-executor5'. SELinux: unrecognized netlink message: protocol=0 nlmsg_type=770 sclass=netlink_route_socket pig=11642 comm=syz-executor0 netlink: 4 bytes leftover after parsing attributes in process `syz-executor5'. FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem SELinux: unrecognized netlink message: protocol=0 nlmsg_type=770 sclass=netlink_route_socket pig=11664 comm=syz-executor0 SELinux: unrecognized netlink message: protocol=0 nlmsg_type=770 sclass=netlink_route_socket pig=11700 comm=syz-executor5 SELinux: unrecognized netlink message: protocol=0 nlmsg_type=770 sclass=netlink_route_socket pig=11706 comm=syz-executor0 FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem SELinux: unrecognized netlink message: protocol=0 nlmsg_type=770 sclass=netlink_route_socket pig=11768 comm=syz-executor5 FAT-fs (loop1): invalid media value (0x48) SELinux: unrecognized netlink message: protocol=0 nlmsg_type=770 sclass=netlink_route_socket pig=11791 comm=syz-executor5 FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop6): invalid media value (0x48) FAT-fs (loop2): invalid media value (0x48) FAT-fs (loop2): Can't find a valid FAT filesystem FAT-fs (loop6): Can't find a valid FAT filesystem FAT-fs (loop1): invalid media value (0x48) FAT-fs (loop1): Can't find a valid FAT filesystem FAT-fs (loop6): invalid media value (0x48) FAT-fs (loop6): Can't find a valid FAT filesystem FAT-fs (loop2): invalid media value (0x48) FAT-fs (loop2): Can't find a valid FAT filesystem