============================= WARNING: suspicious RCU usage 4.19.0-rc3+ #236 Not tainted ----------------------------- include/net/inet_sock.h:136 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz-executor4/6970: #0: 00000000f7cfa1ff (sk_lock-AF_INET6){+.+.}, at: lock_sock include/net/sock.h:1491 [inline] #0: 00000000f7cfa1ff (sk_lock-AF_INET6){+.+.}, at: inet_csk_accept+0xba/0xe70 net/ipv4/inet_connection_sock.c:442 stack backtrace: CPU: 1 PID: 6970 Comm: syz-executor4 Not tainted 4.19.0-rc3+ #236 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1c4/0x2b4 lib/dump_stack.c:113 lockdep_rcu_suspicious+0x14a/0x153 kernel/locking/lockdep.c:4537 ireq_opt_deref include/net/inet_sock.h:135 [inline] inet_csk_route_req+0x977/0xde0 net/ipv4/inet_connection_sock.c:547 dccp_v4_send_response+0xb4/0x6d0 net/dccp/ipv4.c:485 dccp_v4_conn_request+0xc81/0x1390 net/dccp/ipv4.c:634 dccp_v6_conn_request+0xdb9/0x1660 net/dccp/ipv6.c:317 dccp_rcv_state_process+0x6f7/0x1a32 net/dccp/input.c:612 dccp_v4_do_rcv+0x102/0x180 net/dccp/ipv4.c:683 dccp_v6_do_rcv+0x99d/0xbf0 net/dccp/ipv6.c:579 sk_backlog_rcv include/net/sock.h:931 [inline] __release_sock+0x12f/0x3a0 net/core/sock.c:2336 release_sock+0xad/0x2c0 net/core/sock.c:2849 inet_csk_wait_for_connect net/ipv4/inet_connection_sock.c:409 [inline] inet_csk_accept+0x4f8/0xe70 net/ipv4/inet_connection_sock.c:460 inet_accept+0x14b/0x9e0 net/ipv4/af_inet.c:734 __sys_accept4+0x3b2/0x8a0 net/socket.c:1588 __do_sys_accept net/socket.c:1629 [inline] __se_sys_accept net/socket.c:1626 [inline] __x64_sys_accept+0x75/0xb0 net/socket.c:1626 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x4572d9 Code: fd b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 cb b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007fd797605c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002b RAX: ffffffffffffffda RBX: 00007fd7976066d4 RCX: 00000000004572d9 RDX: 0000000020000080 RSI: 0000000000000000 RDI: 0000000000000007 RBP: 0000000000930140 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff R13: 00000000004cb620 R14: 00000000004c321a R15: 0000000000000001 ============================= WARNING: suspicious RCU usage 4.19.0-rc3+ #236 Not tainted ----------------------------- include/net/inet_sock.h:136 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz-executor4/6970: #0: 00000000f7cfa1ff (sk_lock-AF_INET6){+.+.}, at: lock_sock include/net/sock.h:1491 [inline] #0: 00000000f7cfa1ff (sk_lock-AF_INET6){+.+.}, at: inet_csk_accept+0xba/0xe70 net/ipv4/inet_connection_sock.c:442 stack backtrace: CPU: 1 PID: 6970 Comm: syz-executor4 Not tainted 4.19.0-rc3+ #236 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1c4/0x2b4 lib/dump_stack.c:113 lockdep_rcu_suspicious+0x14a/0x153 kernel/locking/lockdep.c:4537 ireq_opt_deref include/net/inet_sock.h:135 [inline] dccp_v4_send_response+0x537/0x6d0 net/dccp/ipv4.c:496 dccp_v4_conn_request+0xc81/0x1390 net/dccp/ipv4.c:634 dccp_v6_conn_request+0xdb9/0x1660 net/dccp/ipv6.c:317 dccp_rcv_state_process+0x6f7/0x1a32 net/dccp/input.c:612 dccp_v4_do_rcv+0x102/0x180 net/dccp/ipv4.c:683 dccp_v6_do_rcv+0x99d/0xbf0 net/dccp/ipv6.c:579 sk_backlog_rcv include/net/sock.h:931 [inline] __release_sock+0x12f/0x3a0 net/core/sock.c:2336 release_sock+0xad/0x2c0 net/core/sock.c:2849 inet_csk_wait_for_connect net/ipv4/inet_connection_sock.c:409 [inline] inet_csk_accept+0x4f8/0xe70 net/ipv4/inet_connection_sock.c:460 inet_accept+0x14b/0x9e0 net/ipv4/af_inet.c:734 __sys_accept4+0x3b2/0x8a0 net/socket.c:1588 __do_sys_accept net/socket.c:1629 [inline] __se_sys_accept net/socket.c:1626 [inline] __x64_sys_accept+0x75/0xb0 net/socket.c:1626 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x4572d9 Code: fd b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 cb b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 RSP: 002b:00007fd797605c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002b RAX: ffffffffffffffda RBX: 00007fd7976066d4 RCX: 00000000004572d9 RDX: 0000000020000080 RSI: 0000000000000000 RDI: 0000000000000007 RBP: 0000000000930140 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff R13: 00000000004cb620 R14: 00000000004c321a R15: 0000000000000001 dccp_close: ABORT with 4096 bytes unread dccp_close: ABORT with 1 bytes unread dccp_close: ABORT with 1 bytes unread dccp_close: ABORT with 4096 bytes unread dccp_close: ABORT with 4096 bytes unread dccp_close: ABORT with 4096 bytes unread dccp_close: ABORT with 4096 bytes unread IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready ISOFS: Unable to identify CD-ROM format. IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details. IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready ISOFS: Unable to identify CD-ROM format. IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready ISOFS: Unable to identify CD-ROM format. ISOFS: Unable to identify CD-ROM format.