====================================================== [ INFO: possible circular locking dependency detected ] 4.9.110-g00a0bcb #4 Not tainted ------------------------------------------------------- syz-executor3/7747 is trying to acquire lock: FAT-fs (loop6): bogus number of reserved sectors FAT-fs (loop6): Can't find a valid FAT filesystem (sk_lock-AF_INET){+.+.+.}, at: [] lock_sock include/net/sock.h:1404 [inline] (sk_lock-AF_INET){+.+.+.}, 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 tcp_setsockopt+0x88/0xe0 net/ipv4/tcp.c:2758 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-executor3/7747: #0: (rtnl_mutex){+.+.+.}, at: [] rtnl_lock+0x17/0x20 net/core/rtnetlink.c:70 stack backtrace: CPU: 0 PID: 7747 Comm: syz-executor3 Not tainted 4.9.110-g00a0bcb #4 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 ffff8801bca67748 ffffffff81eb2329 ffffffff855e7ec0 ffffffff8559d0a0 ffffffff855e7ec0 ffff8801bb7e50e8 ffff8801bb7e4800 ffff8801bca67790 ffffffff814262d4 0000000000000001 00000000bb7e4800 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 [] tcp_setsockopt+0x88/0xe0 net/ipv4/tcp.c:2758 [] 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 EXT4-fs (loop1): mounting ext3 file system using the ext4 subsystem IPVS: Creating netns size=2536 id=14 EXT4-fs (loop1): unsupported inode size: 48170 IPVS: Creating netns size=2536 id=15 FAT-fs (loop6): bogus number of reserved sectors FAT-fs (loop6): Can't find a valid FAT filesystem EXT4-fs (loop1): mounting ext3 file system using the ext4 subsystem EXT4-fs (loop1): unsupported inode size: 48170 EXT4-fs error (device loop5): ext4_iget:4557: inode #2: comm syz-executor5: root inode unallocated EXT4-fs (loop5): get root inode failed EXT4-fs (loop5): mount failed IPv6: ADDRCONF(NETDEV_UP): bond_slave_0: link is not ready IPv6: ADDRCONF(NETDEV_UP): bond_slave_1: link is not ready IPv6: ADDRCONF(NETDEV_UP): team_slave_0: link is not ready IPv6: ADDRCONF(NETDEV_UP): team_slave_1: link is not ready TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies. Check SNMP counters. IPv6: ADDRCONF(NETDEV_CHANGE): bond_slave_0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_bond: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): bond_slave_1: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_bond: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_team: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_1: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_team: link becomes ready TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies. Check SNMP counters. IPVS: Creating netns size=2536 id=16 IPv6: ADDRCONF(NETDEV_UP): veth0_to_bridge: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth1_to_bridge: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth0_to_bond: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth1_to_bond: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth0_to_team: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth1_to_team: link is not ready IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_bridge: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_bridge: link becomes ready IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth1: link is not ready IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready capability: warning: `syz-executor6' uses 32-bit capabilities (legacy support in use) TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies. Check SNMP counters. selinux_nlmsg_perm: 136 callbacks suppressed SELinux: unrecognized netlink message: protocol=9 nlmsg_type=258 sclass=netlink_audit_socket pig=8332 comm=syz-executor5 SELinux: unrecognized netlink message: protocol=9 nlmsg_type=18432 sclass=netlink_audit_socket pig=8332 comm=syz-executor5 SELinux: unrecognized netlink message: protocol=9 nlmsg_type=35074 sclass=netlink_audit_socket pig=8332 comm=syz-executor5 SELinux: unrecognized netlink message: protocol=9 nlmsg_type=1200 sclass=netlink_audit_socket pig=8332 comm=syz-executor5 SELinux: unrecognized netlink message: protocol=9 nlmsg_type=10277 sclass=netlink_audit_socket pig=8332 comm=syz-executor5 SELinux: unrecognized netlink message: protocol=9 nlmsg_type=7716 sclass=netlink_audit_socket pig=8332 comm=syz-executor5 SELinux: unrecognized netlink message: protocol=9 nlmsg_type=53029 sclass=netlink_audit_socket pig=8332 comm=syz-executor5 SELinux: unrecognized netlink message: protocol=9 nlmsg_type=12745 sclass=netlink_audit_socket pig=8332 comm=syz-executor5 SELinux: unrecognized netlink message: protocol=9 nlmsg_type=31352 sclass=netlink_audit_socket pig=8332 comm=syz-executor5 SELinux: unrecognized netlink message: protocol=9 nlmsg_type=0 sclass=netlink_audit_socket pig=8332 comm=syz-executor5 IPVS: Creating netns size=2536 id=17 IPv6: ADDRCONF(NETDEV_UP): veth0_to_bridge: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth1_to_bridge: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth0_to_bond: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth1_to_bond: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth0_to_team: link is not ready IPv6: ADDRCONF(NETDEV_UP): veth1_to_team: link is not ready IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_bridge: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_bridge: link becomes ready