============================= WARNING: suspicious RCU usage 4.14.307-syzkaller #0 Not tainted ----------------------------- net/tipc/bearer.c:177 suspicious rcu_dereference_protected() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 2 locks held by syz-executor.4/11286: #0: (cb_lock){++++}, at: [] genl_rcv+0x15/0x40 net/netlink/genetlink.c:635 #1: (genl_mutex){+.+.}, at: [] genl_lock net/netlink/genetlink.c:33 [inline] #1: (genl_mutex){+.+.}, at: [] genl_rcv_msg+0x112/0x140 net/netlink/genetlink.c:623 stack backtrace: CPU: 1 PID: 11286 Comm: syz-executor.4 Not tainted 4.14.307-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 tipc_bearer_find+0x1ff/0x2f0 net/tipc/bearer.c:177 tipc_nl_compat_link_set+0x40b/0xb90 net/tipc/netlink_compat.c:807 __tipc_nl_compat_doit net/tipc/netlink_compat.c:316 [inline] tipc_nl_compat_doit+0x192/0x5d0 net/tipc/netlink_compat.c:364 tipc_nl_compat_handle net/tipc/netlink_compat.c:1215 [inline] tipc_nl_compat_recv+0xa0b/0xae0 net/tipc/netlink_compat.c:1297 genl_family_rcv_msg+0x572/0xb20 net/netlink/genetlink.c:600 genl_rcv_msg+0xaf/0x140 net/netlink/genetlink.c:625 netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2461 genl_rcv+0x24/0x40 net/netlink/genetlink.c:636 netlink_unicast_kernel net/netlink/af_netlink.c:1302 [inline] netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1328 netlink_sendmsg+0x651/0xbc0 net/netlink/af_netlink.c:1900 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+0x5e/0xd3 RIP: 0033:0x7f16a22cc0f9 RSP: 002b:00007f16a083e168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f16a23ebf80 RCX: 00007f16a22cc0f9 RDX: 0000000000000000 RSI: 0000000020000680 RDI: 0000000000000003 RBP: 00007f16a2327ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffd7e80a63f R14: 00007f16a083e300 R15: 0000000000022000 audit: type=1326 audit(1678107849.075:12): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=11393 comm="syz-executor.4" exe="/root/syz-executor.4" sig=31 arch=c000003e syscall=202 compat=0 ip=0x7f16a22cc0f9 code=0x0 TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1 capability: warning: `syz-executor.5' uses deprecated v2 capabilities in a way that may be insecure Bluetooth: hci0 command 0x0401 tx timeout Bluetooth: hci1 command 0x0401 tx timeout EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue audit: type=1804 audit(1678107856.905:13): pid=12238 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir163085043/syzkaller.olUcCK/177/file0/bus" dev="loop2" ino=18 res=1 Unknown ioctl -805268450 FAT-fs (loop2): error, fat_get_cluster: invalid start cluster (i_pos 1, start 00000900) FAT-fs (loop2): Filesystem has been set read-only print_req_error: I/O error, dev loop2, sector 2 Buffer I/O error on dev loop2, logical block 2, async page read print_req_error: I/O error, dev loop2, sector 3 Buffer I/O error on dev loop2, logical block 3, async page read print_req_error: I/O error, dev loop2, sector 4 Buffer I/O error on dev loop2, logical block 4, async page read print_req_error: I/O error, dev loop2, sector 5 Buffer I/O error on dev loop2, logical block 5, async page read print_req_error: I/O error, dev loop2, sector 6 Buffer I/O error on dev loop2, logical block 6, async page read print_req_error: I/O error, dev loop2, sector 7 Buffer I/O error on dev loop2, logical block 7, async page read EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! EXT4-fs (loop4): encrypted files will use data=ordered instead of data journaling mode EXT4-fs (loop4): couldn't mount as ext2 due to feature incompatibilities