============================= 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.5/9918: #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: 0 PID: 9918 Comm: syz-executor.5 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:0x7fe5da8f40f9 RSP: 002b:00007fe5d8e66168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007fe5daa13f80 RCX: 00007fe5da8f40f9 RDX: 0000000000000000 RSI: 0000000020000380 RDI: 0000000000000003 RBP: 00007fe5da94fae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff84dc024f R14: 00007fe5d8e66300 R15: 0000000000022000 IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready FAT-fs (loop0): mounting with "discard" option, but the device does not support discard IPv6: ADDRCONF(NETDEV_CHANGE): vxcan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vxcan1: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vxcan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vxcan1: link becomes ready syz-executor.0 uses obsolete (PF_INET,SOCK_PACKET) 9pnet: Insufficient options for proto=fd print_req_error: I/O error, dev loop5, sector 0 ====================================================== WARNING: the mand mount option is being deprecated and will be removed in v5.15! ====================================================== audit: type=1800 audit(1678006774.346:2): pid=10388 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="bus" dev="sda1" ino=13981 res=0 9pnet: Insufficient options for proto=fd 9pnet: Insufficient options for proto=fd audit: type=1804 audit(1678006776.456:3): pid=10509 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.4" name="/root/syzkaller-testdir2507236484/syzkaller.kDMvLQ/62/file0" dev="sda1" ino=14024 res=1 audit: type=1800 audit(1678006776.586:4): pid=10540 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.4" name="file0" dev="sda1" ino=13885 res=0 9pnet: Insufficient options for proto=fd FAT-fs (loop3): mounting with "discard" option, but the device does not support discard IPVS: ftp: loaded support on port[0] = 21 audit: type=1804 audit(1678006777.016:5): pid=10636 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.0" name="/root/syzkaller-testdir432915038/syzkaller.yBSAv9/70/file0" dev="sda1" ino=14026 res=1 9pnet: Insufficient options for proto=fd 9pnet: Insufficient options for proto=fd L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. hrtimer: interrupt took 24152 ns ntfs: volume version 3.1. ntfs: (device loop5): ntfs_cluster_alloc(): Failed to allocate clusters, aborting (error -28). ntfs: (device loop5): ntfs_attr_extend_allocation(): Cannot extend allocation of inode 0x43, attribute type 0x80, because the allocation of clusters failed with error code -28. ntfs: (device loop5): ntfs_write_block(): Writing beyond initialized size is not supported yet. Sorry. ntfs: (device loop5): ntfs_cluster_alloc(): Failed to allocate clusters, aborting (error -28). ntfs: (device loop5): ntfs_attr_extend_allocation(): Cannot extend allocation of inode 0x43, attribute type 0x80, because the allocation of clusters failed with error code -28. XFS (loop3): Mounting V4 Filesystem XFS (loop3): Ending clean mount XFS (loop3): Unmounting Filesystem ntfs: volume version 3.1. ntfs: (device loop5): ntfs_cluster_alloc(): Failed to allocate clusters, aborting (error -28). ntfs: (device loop5): ntfs_attr_extend_allocation(): Cannot extend allocation of inode 0x43, attribute type 0x80, because the allocation of clusters failed with error code -28. ntfs: (device loop5): ntfs_write_block(): Writing beyond initialized size is not supported yet. Sorry. ntfs: (device loop5): ntfs_cluster_alloc(): Failed to allocate clusters, aborting (error -28). ntfs: (device loop5): ntfs_attr_extend_allocation(): Cannot extend allocation of inode 0x43, attribute type 0x80, because the allocation of clusters failed with error code -28. XFS (loop3): Mounting V4 Filesystem XFS (loop3): Ending clean mount XFS (loop3): Unmounting Filesystem