====================================================== WARNING: possible circular locking dependency detected 4.14.171-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.3/7284 is trying to acquire lock: (rtnl_mutex){+.+.}, at: [] rtnl_lock+0x17/0x20 net/core/rtnetlink.c:72 but task is already holding lock: (&xt[i].mutex){+.+.}, at: [] xt_find_table_lock+0x3c/0x3d0 net/netfilter/x_tables.c:1092 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&xt[i].mutex){+.+.}: lock_acquire+0x16f/0x430 kernel/locking/lockdep.c:3994 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xe8/0x1470 kernel/locking/mutex.c:893 mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:908 xt_find_target+0x3e/0x1e0 net/netfilter/x_tables.c:232 xt_request_find_target net/netfilter/x_tables.c:261 [inline] xt_request_find_target+0x74/0xe0 net/netfilter/x_tables.c:254 ipt_init_target+0xce/0x290 net/sched/act_ipt.c:45 __tcf_ipt_init+0x48c/0xb50 net/sched/act_ipt.c:168 tcf_ipt_init+0x4e/0x60 net/sched/act_ipt.c:202 tcf_action_init_1+0x53c/0xaa0 net/sched/act_api.c:682 tcf_action_init+0x2ab/0x480 net/sched/act_api.c:751 tcf_action_add net/sched/act_api.c:1079 [inline] tc_ctl_action+0x30a/0x548 net/sched/act_api.c:1131 rtnetlink_rcv_msg+0x3da/0xb70 net/core/rtnetlink.c:4315 netlink_rcv_skb+0x14f/0x3c0 net/netlink/af_netlink.c:2432 rtnetlink_rcv+0x1d/0x30 net/core/rtnetlink.c:4327 netlink_unicast_kernel net/netlink/af_netlink.c:1286 [inline] netlink_unicast+0x44d/0x650 net/netlink/af_netlink.c:1312 netlink_sendmsg+0x7c4/0xc60 net/netlink/af_netlink.c:1877 sock_sendmsg_nosec net/socket.c:646 [inline] sock_sendmsg+0xce/0x110 net/socket.c:656 ___sys_sendmsg+0x70a/0x840 net/socket.c:2062 __sys_sendmsg+0xb9/0x140 net/socket.c:2096 SYSC_sendmsg net/socket.c:2107 [inline] SyS_sendmsg+0x2d/0x50 net/socket.c:2103 do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 -> #0 (rtnl_mutex){+.+.}: check_prev_add kernel/locking/lockdep.c:1901 [inline] check_prevs_add kernel/locking/lockdep.c:2018 [inline] validate_chain kernel/locking/lockdep.c:2460 [inline] __lock_acquire+0x2cb3/0x4620 kernel/locking/lockdep.c:3487 lock_acquire+0x16f/0x430 kernel/locking/lockdep.c:3994 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xe8/0x1470 kernel/locking/mutex.c:893 mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:908 rtnl_lock+0x17/0x20 net/core/rtnetlink.c:72 unregister_netdevice_notifier+0x5f/0x2c0 net/core/dev.c:1634 tee_tg_destroy+0x61/0xc0 net/netfilter/xt_TEE.c:123 cleanup_entry+0x17d/0x230 net/ipv4/netfilter/ip_tables.c:666 __do_replace+0x3c5/0x5b0 net/ipv4/netfilter/ip_tables.c:1086 do_replace net/ipv4/netfilter/ip_tables.c:1142 [inline] do_ipt_set_ctl+0x296/0x3ee net/ipv4/netfilter/ip_tables.c:1674 nf_sockopt net/netfilter/nf_sockopt.c:106 [inline] nf_setsockopt+0x67/0xc0 net/netfilter/nf_sockopt.c:115 ip_setsockopt net/ipv4/ip_sockglue.c:1255 [inline] ip_setsockopt+0x9b/0xb0 net/ipv4/ip_sockglue.c:1240 tcp_setsockopt net/ipv4/tcp.c:2826 [inline] tcp_setsockopt+0x84/0xd0 net/ipv4/tcp.c:2820 sock_common_setsockopt+0x94/0xd0 net/core/sock.c:2968 SYSC_setsockopt net/socket.c:1865 [inline] SyS_setsockopt+0x13c/0x210 net/socket.c:1844 do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&xt[i].mutex); lock(rtnl_mutex); lock(&xt[i].mutex); lock(rtnl_mutex); *** DEADLOCK *** 1 lock held by syz-executor.3/7284: #0: (&xt[i].mutex){+.+.}, at: [] xt_find_table_lock+0x3c/0x3d0 net/netfilter/x_tables.c:1092 stack backtrace: CPU: 0 PID: 7284 Comm: syz-executor.3 Not tainted 4.14.171-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x142/0x197 lib/dump_stack.c:58 print_circular_bug.isra.0.cold+0x1cc/0x28f kernel/locking/lockdep.c:1258 check_prev_add kernel/locking/lockdep.c:1901 [inline] check_prevs_add kernel/locking/lockdep.c:2018 [inline] validate_chain kernel/locking/lockdep.c:2460 [inline] __lock_acquire+0x2cb3/0x4620 kernel/locking/lockdep.c:3487 lock_acquire+0x16f/0x430 kernel/locking/lockdep.c:3994 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xe8/0x1470 kernel/locking/mutex.c:893 mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:908 rtnl_lock+0x17/0x20 net/core/rtnetlink.c:72 unregister_netdevice_notifier+0x5f/0x2c0 net/core/dev.c:1634 tee_tg_destroy+0x61/0xc0 net/netfilter/xt_TEE.c:123 cleanup_entry+0x17d/0x230 net/ipv4/netfilter/ip_tables.c:666 __do_replace+0x3c5/0x5b0 net/ipv4/netfilter/ip_tables.c:1086 do_replace net/ipv4/netfilter/ip_tables.c:1142 [inline] do_ipt_set_ctl+0x296/0x3ee net/ipv4/netfilter/ip_tables.c:1674 nf_sockopt net/netfilter/nf_sockopt.c:106 [inline] nf_setsockopt+0x67/0xc0 net/netfilter/nf_sockopt.c:115 ip_setsockopt net/ipv4/ip_sockglue.c:1255 [inline] ip_setsockopt+0x9b/0xb0 net/ipv4/ip_sockglue.c:1240 tcp_setsockopt net/ipv4/tcp.c:2826 [inline] tcp_setsockopt+0x84/0xd0 net/ipv4/tcp.c:2820 sock_common_setsockopt+0x94/0xd0 net/core/sock.c:2968 SYSC_setsockopt net/socket.c:1865 [inline] SyS_setsockopt+0x13c/0x210 net/socket.c:1844 do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 RIP: 0033:0x45ef5a RSP: 002b:00007ffec6d7c9a8 EFLAGS: 00000202 ORIG_RAX: 0000000000000036 RAX: ffffffffffffffda RBX: 00007ffec6d7c9d0 RCX: 000000000045ef5a RDX: 0000000000000040 RSI: 0000000000000000 RDI: 0000000000000003 RBP: 000000000071fe80 R08: 0000000000000408 R09: 0000000000004000 R10: 000000000071eaa0 R11: 0000000000000202 R12: 0000000000000003 R13: 0000000000000000 R14: 0000000000000000 R15: 000000000071ea40 f2fs_msg: 8 callbacks suppressed F2FS-fs (loop4): Magic Mismatch, valid(0xf2f52010) - read(0x0) F2FS-fs (loop4): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop4): Invalid blocksize (1), supports only 4KB overlayfs: fs on 'file0' does not support file handles, falling back to index=off. F2FS-fs (loop4): Can't find valid F2FS filesystem in 2th superblock F2FS-fs (loop4): Magic Mismatch, valid(0xf2f52010) - read(0x0) F2FS-fs (loop4): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop4): Invalid blocksize (1), supports only 4KB F2FS-fs (loop4): Can't find valid F2FS filesystem in 2th superblock F2FS-fs (loop4): Magic Mismatch, valid(0xf2f52010) - read(0x0) F2FS-fs (loop4): Can't find valid F2FS filesystem in 1th superblock selinux_nlmsg_perm: 70 callbacks suppressed SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=21562 comm=syz-executor.4 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=21562 comm=syz-executor.4 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=21562 comm=syz-executor.4 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=21562 comm=syz-executor.4 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=21562 comm=syz-executor.4 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=21562 comm=syz-executor.4 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=21562 comm=syz-executor.4 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=21562 comm=syz-executor.4 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=21562 comm=syz-executor.4 SELinux: unrecognized netlink message: protocol=4 nlmsg_type=0 sclass=netlink_tcpdiag_socket pig=21562 comm=syz-executor.4 nla_parse: 5 callbacks suppressed netlink: 28 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 28 bytes leftover after parsing attributes in process `syz-executor.4'. ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' netlink: 28 bytes leftover after parsing attributes in process `syz-executor.4'. ieee80211 phy11: hwaddr 02:00:00:00:0b:00 registered ieee80211 phy12: Selected rate control algorithm 'minstrel_ht' ieee80211 phy12: hwaddr 02:00:00:00:0c:00 registered ieee80211 phy13: Selected rate control algorithm 'minstrel_ht' netlink: 28 bytes leftover after parsing attributes in process `syz-executor.4'. ieee80211 phy13: hwaddr 02:00:00:00:0d:00 registered ieee80211 phy14: Selected rate control algorithm 'minstrel_ht' ieee80211 phy14: hwaddr 02:00:00:00:0e:00 registered ieee80211 phy15: Selected rate control algorithm 'minstrel_ht' ieee80211 phy15: hwaddr 02:00:00:00:0f:00 registered ieee80211 phy16: Selected rate control algorithm 'minstrel_ht' ieee80211 phy16: hwaddr 02:00:00:00:10:00 registered ieee80211 phy17: Selected rate control algorithm 'minstrel_ht' ieee80211 phy17: hwaddr 02:00:00:00:11:00 registered ieee80211 phy18: Selected rate control algorithm 'minstrel_ht' ieee80211 phy18: hwaddr 02:00:00:00:12:00 registered ieee80211 phy19: Selected rate control algorithm 'minstrel_ht' ieee80211 phy19: hwaddr 02:00:00:00:13:00 registered ieee80211 phy20: Selected rate control algorithm 'minstrel_ht' ieee80211 phy20: hwaddr 02:00:00:00:14:00 registered netlink: 28 bytes leftover after parsing attributes in process `syz-executor.5'. netlink: 28 bytes leftover after parsing attributes in process `syz-executor.1'. netlink: 28 bytes leftover after parsing attributes in process `syz-executor.5'. netlink: 28 bytes leftover after parsing attributes in process `syz-executor.4'. ieee80211 phy21: Selected rate control algorithm 'minstrel_ht' ieee80211 phy21: hwaddr 02:00:00:00:15:00 registered netlink: 28 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 28 bytes leftover after parsing attributes in process `syz-executor.1'. Dead loop on virtual device ip6_vti0, fix it urgently! Dead loop on virtual device ip6_vti0, fix it urgently! Dead loop on virtual device ip6_vti0, fix it urgently!