======================================================
WARNING: possible circular locking dependency detected
4.14.291-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.4/12192 is trying to acquire lock:
(&xt[i].mutex){+.+.}, at: [<ffffffff85f16a83>] target_revfn+0x43/0x210 net/netfilter/x_tables.c:354
but task is already holding lock:
(&table[i].mutex){+.+.}, at: [<ffffffff85e42bc6>] nfnl_lock net/netfilter/nfnetlink.c:61 [inline]
(&table[i].mutex){+.+.}, at: [<ffffffff85e42bc6>] nfnetlink_rcv_msg+0x726/0xc00 net/netfilter/nfnetlink.c:209
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (&table[i].mutex){+.+.}:
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
nf_tables_netdev_event+0x10d/0x4d0 net/netfilter/nf_tables_netdev.c:122
notifier_call_chain+0x108/0x1a0 kernel/notifier.c:93
call_netdevice_notifiers_info net/core/dev.c:1667 [inline]
call_netdevice_notifiers net/core/dev.c:1683 [inline]
rollback_registered_many+0x765/0xbb0 net/core/dev.c:7211
rollback_registered+0xca/0x170 net/core/dev.c:7253
unregister_netdevice_queue+0x1b4/0x360 net/core/dev.c:8274
unregister_netdevice include/linux/netdevice.h:2444 [inline]
ppp_release+0x177/0x1a0 drivers/net/ppp/ppp_generic.c:410
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:191 [inline]
exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
entry_SYSCALL_64_after_hwframe+0x46/0xbb
-> #1 (rtnl_mutex){+.+.}:
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
unregister_netdevice_notifier+0x5e/0x2b0 net/core/dev.c:1630
tee_tg_destroy+0x5c/0xb0 net/netfilter/xt_TEE.c:123
cleanup_entry+0x1fd/0x2d0 net/ipv4/netfilter/ip_tables.c:666
__do_replace+0x38d/0x570 net/ipv4/netfilter/ip_tables.c:1086
do_replace net/ipv4/netfilter/ip_tables.c:1142 [inline]
do_ipt_set_ctl+0x256/0x3a0 net/ipv4/netfilter/ip_tables.c:1676
nf_sockopt net/netfilter/nf_sockopt.c:106 [inline]
nf_setsockopt+0x5f/0xb0 net/netfilter/nf_sockopt.c:115
ip_setsockopt net/ipv4/ip_sockglue.c:1255 [inline]
ip_setsockopt+0x94/0xb0 net/ipv4/ip_sockglue.c:1240
tcp_setsockopt+0x7b/0xc0 net/ipv4/tcp.c:2830
SYSC_setsockopt net/socket.c:1865 [inline]
SyS_setsockopt+0x110/0x1e0 net/socket.c:1844
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
-> #0 (&xt[i].mutex){+.+.}:
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
target_revfn+0x43/0x210 net/netfilter/x_tables.c:354
xt_find_revision+0x15e/0x1d0 net/netfilter/x_tables.c:378
nfnl_compat_get+0x1f7/0x870 net/netfilter/nft_compat.c:678
nfnetlink_rcv_msg+0x9bb/0xc00 net/netfilter/nfnetlink.c:214
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2454
nfnetlink_rcv+0x1ab/0x1da0 net/netfilter/nfnetlink.c:515
netlink_unicast_kernel net/netlink/af_netlink.c:1296 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1322
netlink_sendmsg+0x648/0xbc0 net/netlink/af_netlink.c:1893
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
other info that might help us debug this:
Chain exists of:
&xt[i].mutex --> rtnl_mutex --> &table[i].mutex
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&table[i].mutex);
lock(rtnl_mutex);
lock(&table[i].mutex);
lock(&xt[i].mutex);
*** DEADLOCK ***
1 lock held by syz-executor.4/12192:
#0: (&table[i].mutex){+.+.}, at: [<ffffffff85e42bc6>] nfnl_lock net/netfilter/nfnetlink.c:61 [inline]
#0: (&table[i].mutex){+.+.}, at: [<ffffffff85e42bc6>] nfnetlink_rcv_msg+0x726/0xc00 net/netfilter/nfnetlink.c:209
stack backtrace:
CPU: 0 PID: 12192 Comm: syz-executor.4 Not tainted 4.14.291-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258
check_prev_add kernel/locking/lockdep.c:1905 [inline]
check_prevs_add kernel/locking/lockdep.c:2022 [inline]
validate_chain kernel/locking/lockdep.c:2464 [inline]
__lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
target_revfn+0x43/0x210 net/netfilter/x_tables.c:354
xt_find_revision+0x15e/0x1d0 net/netfilter/x_tables.c:378
nfnl_compat_get+0x1f7/0x870 net/netfilter/nft_compat.c:678
nfnetlink_rcv_msg+0x9bb/0xc00 net/netfilter/nfnetlink.c:214
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2454
nfnetlink_rcv+0x1ab/0x1da0 net/netfilter/nfnetlink.c:515
netlink_unicast_kernel net/netlink/af_netlink.c:1296 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1322
netlink_sendmsg+0x648/0xbc0 net/netlink/af_netlink.c:1893
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7fafbb68a279
RSP: 002b:00007fafb9fff168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007fafbb79cf80 RCX: 00007fafbb68a279
RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000000000003
RBP: 00007fafbb6e42e9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffdd4734dcf R14: 00007fafb9fff300 R15: 0000000000022000
TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies. Check SNMP counters.
TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies. Check SNMP counters.
pit: kvm: requested 4190 ns i8254 timer period limited to 500000 ns
kvm: pic: non byte read
TCP: request_sock_TCP: Possible SYN flooding on port 20002. Sending cookies. Check SNMP counters.
device team0 left promiscuous mode
kvm: pic: non byte read
kvm: pic: non byte read
device team_slave_0 left promiscuous mode
kvm: pic: non byte read
kvm: pic: non byte read
device team_slave_1 left promiscuous mode
bridge0: port 3(team0) entered disabled state
kvm: pic: non byte read
kvm: pic: non byte read
kvm: pic: non byte read
kvm: pic: non byte read
kvm: pic: non byte read
8021q: adding VLAN 0 to HW filter on device team0
bond0: Enslaving team0 as an active interface with an up link
pit: kvm: requested 4190 ns i8254 timer period limited to 500000 ns
bond0: Releasing backup interface team0
bridge0: port 3(team0) entered blocking state
bridge0: port 3(team0) entered disabled state
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
device team0 entered promiscuous mode
device team_slave_0 entered promiscuous mode
device team_slave_1 entered promiscuous mode
syz-executor.3 (12240) used greatest stack depth: 23984 bytes left
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
pit: kvm: requested 4190 ns i8254 timer period limited to 500000 ns
pit: kvm: requested 4190 ns i8254 timer period limited to 500000 ns
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
process 'syz-executor.1' launched './file0' with NULL argv: empty string added
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
PM: Marking nosave pages: [mem 0x0009f000-0x000fffff]
PM: Marking nosave pages: [mem 0xbfffd000-0xffffffff]
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
PM: Basic memory bitmaps created
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
PM: Basic memory bitmaps freed
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
PM: Marking nosave pages: [mem 0x0009f000-0x000fffff]
PM: Marking nosave pages: [mem 0xbfffd000-0xffffffff]
PM: Basic memory bitmaps created
PM: Basic memory bitmaps freed
PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
PM: Marking nosave pages: [mem 0x0009f000-0x000fffff]
PM: Marking nosave pages: [mem 0xbfffd000-0xffffffff]
PM: Basic memory bitmaps created
PM: Basic memory bitmaps freed
PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
PM: Marking nosave pages: [mem 0x0009f000-0x000fffff]
PM: Marking nosave pages: [mem 0xbfffd000-0xffffffff]
PM: Basic memory bitmaps created
PM: Basic memory bitmaps freed
(unnamed net_device) (uninitialized): option lacp_rate: mode dependency failed, not supported in mode broadcast(3)
ISO 9660 Extensions: Microsoft Joliet Level 3
isofs_fill_super: get root inode failed
ISO 9660 Extensions: Microsoft Joliet Level 3
isofs_fill_super: get root inode failed
ISO 9660 Extensions: Microsoft Joliet Level 3
isofs_fill_super: get root inode failed
ISO 9660 Extensions: Microsoft Joliet Level 3
isofs_fill_super: get root inode failed
print_req_error: I/O error, dev loop0, sector 4
Buffer I/O error on dev loop0, logical block 1, async page read
ceph: No mds server is up or the cluster is laggy
unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1
ceph: No mds server is up or the cluster is laggy
device geneve3 entered promiscuous mode
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy
ceph: No mds server is up or the cluster is laggy
libceph: connect [d::]:6789 error -101
libceph: mon0 [d::]:6789 connect error
ceph: No mds server is up or the cluster is laggy