IPVS: set_ctl: invalid protocol: 65534 255.255.255.255:20003 ovf IPVS: set_ctl: invalid protocol: 65534 255.255.255.255:20003 ovf ====================================================== WARNING: possible circular locking dependency detected 4.17.0-rc2+ #22 Not tainted ------------------------------------------------------ syz-executor0/6774 is trying to acquire lock: (ptrval) (sk_lock-AF_INET6){+.+.}, at: lock_sock include/net/sock.h:1469 [inline] (ptrval) (sk_lock-AF_INET6){+.+.}, at: tcp_mmap+0x1c7/0x14f0 net/ipv4/tcp.c:1759 but task is already holding lock: (ptrval) (&mm->mmap_sem){++++}, at: vm_mmap_pgoff+0x1a1/0x2a0 mm/util.c:355 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&mm->mmap_sem){++++}: __might_fault+0x155/0x1e0 mm/memory.c:4555 _copy_from_user+0x30/0x150 lib/usercopy.c:10 copy_from_user include/linux/uaccess.h:147 [inline] ipv6_flowlabel_opt+0x258/0x3310 net/ipv6/ip6_flowlabel.c:529 do_ipv6_setsockopt.isra.9+0xb81/0x4680 net/ipv6/ipv6_sockglue.c:803 ipv6_setsockopt+0xbd/0x170 net/ipv6/ipv6_sockglue.c:922 tcp_setsockopt+0x93/0xe0 net/ipv4/tcp.c:3029 sock_common_setsockopt+0x9a/0xe0 net/core/sock.c:3042 dccp_xmit_packet: Payload too large (65423) for featneg. __sys_setsockopt+0x1bd/0x390 net/socket.c:1903 __do_sys_setsockopt net/socket.c:1914 [inline] __se_sys_setsockopt net/socket.c:1911 [inline] __x64_sys_setsockopt+0xbe/0x150 net/socket.c:1911 do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (sk_lock-AF_INET6){+.+.}: lock_acquire+0x1dc/0x520 kernel/locking/lockdep.c:3920 lock_sock_nested+0xd0/0x120 net/core/sock.c:2844 lock_sock include/net/sock.h:1469 [inline] tcp_mmap+0x1c7/0x14f0 net/ipv4/tcp.c:1759 sock_mmap+0x8e/0xc0 net/socket.c:1144 call_mmap include/linux/fs.h:1789 [inline] mmap_region+0xd13/0x1820 mm/mmap.c:1723 do_mmap+0xc79/0x11d0 mm/mmap.c:1494 do_mmap_pgoff include/linux/mm.h:2237 [inline] vm_mmap_pgoff+0x1fb/0x2a0 mm/util.c:357 ksys_mmap_pgoff+0x4c9/0x640 mm/mmap.c:1544 __do_sys_mmap arch/x86/kernel/sys_x86_64.c:100 [inline] __se_sys_mmap arch/x86/kernel/sys_x86_64.c:91 [inline] __x64_sys_mmap+0xe9/0x1b0 arch/x86/kernel/sys_x86_64.c:91 do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&mm->mmap_sem); lock(sk_lock-AF_INET6); lock(&mm->mmap_sem); lock(sk_lock-AF_INET6); *** DEADLOCK *** 1 lock held by syz-executor0/6774: #0: (ptrval) (&mm->mmap_sem){++++}, at: vm_mmap_pgoff+0x1a1/0x2a0 mm/util.c:355 stack backtrace: CPU: 1 PID: 6774 Comm: syz-executor0 Not tainted 4.17.0-rc2+ #22 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+0x1b9/0x294 lib/dump_stack.c:113 print_circular_bug.isra.36.cold.54+0x1bd/0x27d kernel/locking/lockdep.c:1223 check_prev_add kernel/locking/lockdep.c:1863 [inline] check_prevs_add kernel/locking/lockdep.c:1976 [inline] validate_chain kernel/locking/lockdep.c:2417 [inline] __lock_acquire+0x343e/0x5140 kernel/locking/lockdep.c:3431 lock_acquire+0x1dc/0x520 kernel/locking/lockdep.c:3920 lock_sock_nested+0xd0/0x120 net/core/sock.c:2844 lock_sock include/net/sock.h:1469 [inline] tcp_mmap+0x1c7/0x14f0 net/ipv4/tcp.c:1759 sock_mmap+0x8e/0xc0 net/socket.c:1144 call_mmap include/linux/fs.h:1789 [inline] mmap_region+0xd13/0x1820 mm/mmap.c:1723 do_mmap+0xc79/0x11d0 mm/mmap.c:1494 do_mmap_pgoff include/linux/mm.h:2237 [inline] vm_mmap_pgoff+0x1fb/0x2a0 mm/util.c:357 ksys_mmap_pgoff+0x4c9/0x640 mm/mmap.c:1544 __do_sys_mmap arch/x86/kernel/sys_x86_64.c:100 [inline] __se_sys_mmap arch/x86/kernel/sys_x86_64.c:91 [inline] __x64_sys_mmap+0xe9/0x1b0 arch/x86/kernel/sys_x86_64.c:91 do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x455979 RSP: 002b:00007f7090246c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 RAX: ffffffffffffffda RBX: 00007f70902476d4 RCX: 0000000000455979 RDX: 0000000000000000 RSI: 0000000000001000 RDI: 000000002000e000 RBP: 000000000072bea0 R08: 0000000000000013 R09: 0000000000000000 R10: 0000000000000012 R11: 0000000000000246 R12: 00000000ffffffff R13: 00000000000003fe R14: 00000000006f9070 R15: 0000000000000000 sctp: [Deprecated]: syz-executor4 (pid 6856) Use of int in max_burst socket option deprecated. Use struct sctp_assoc_value instead xt_ipvs: protocol family 7 not supported kernel msg: ebtables bug: please report to author: bad policy kernel msg: ebtables bug: please report to author: bad policy sctp: [Deprecated]: syz-executor4 (pid 6856) Use of int in max_burst socket option deprecated. Use struct sctp_assoc_value instead xt_ipvs: protocol family 7 not supported x_tables: eb_tables: arpreply target: used from hooks OUTPUT, but only usable from PREROUTING netlink: 3 bytes leftover after parsing attributes in process `syz-executor2'. IPVS: set_ctl: invalid protocol: 8 172.20.20.187:20001 nq x_tables: eb_tables: arpreply target: used from hooks OUTPUT, but only usable from PREROUTING netlink: 12 bytes leftover after parsing attributes in process `syz-executor2'. IPVS: set_ctl: invalid protocol: 8 172.20.20.187:20001 nq netlink: 3 bytes leftover after parsing attributes in process `syz-executor2'. netlink: 3 bytes leftover after parsing attributes in process `syz-executor2'. netlink: 3 bytes leftover after parsing attributes in process `syz-executor2'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor2'. kernel msg: ebtables bug: please report to author: Chains don't start at beginning kernel msg: ebtables bug: please report to author: Chains don't start at beginning kernel msg: ebtables bug: please report to author: Wrong len argument nla_parse: 1 callbacks suppressed netlink: 20 bytes leftover after parsing attributes in process `syz-executor2'. sctp: [Deprecated]: syz-executor1 (pid 7123) Use of int in maxseg socket option. Use struct sctp_assoc_value instead sctp: [Deprecated]: syz-executor1 (pid 7123) Use of int in maxseg socket option. Use struct sctp_assoc_value instead netlink: 20 bytes leftover after parsing attributes in process `syz-executor2'. syz-executor5 uses obsolete (PF_INET,SOCK_PACKET) kernel msg: ebtables bug: please report to author: Wrong len argument netlink: 'syz-executor7': attribute type 1 has an invalid length. netlink: 'syz-executor7': attribute type 1 has an invalid length. netlink: 'syz-executor0': attribute type 1 has an invalid length. netlink: 'syz-executor0': attribute type 1 has an invalid length. netlink: 17 bytes leftover after parsing attributes in process `syz-executor6'. netlink: 17 bytes leftover after parsing attributes in process `syz-executor6'. netlink: 17 bytes leftover after parsing attributes in process `syz-executor6'. Can not set IPV6_FL_F_REFLECT if flowlabel_consistency sysctl is enable can: request_module (can-proto-5) failed. Can not set IPV6_FL_F_REFLECT if flowlabel_consistency sysctl is enable can: request_module (can-proto-5) failed. Can not set IPV6_FL_F_REFLECT if flowlabel_consistency sysctl is enable kernel msg: ebtables bug: please report to author: Wrong len argument Can not set IPV6_FL_F_REFLECT if flowlabel_consistency sysctl is enable Can not set IPV6_FL_F_REFLECT if flowlabel_consistency sysctl is enable Can not set IPV6_FL_F_REFLECT if flowlabel_consistency sysctl is enable Can not set IPV6_FL_F_REFLECT if flowlabel_consistency sysctl is enable Can not set IPV6_FL_F_REFLECT if flowlabel_consistency sysctl is enable Can not set IPV6_FL_F_REFLECT if flowlabel_consistency sysctl is enable Can not set IPV6_FL_F_REFLECT if flowlabel_consistency sysctl is enable netlink: 4 bytes leftover after parsing attributes in process `syz-executor3'. netlink: 8 bytes leftover after parsing attributes in process `syz-executor4'. netlink: 4 bytes leftover after parsing attributes in process `syz-executor3'. netlink: 8 bytes leftover after parsing attributes in process `syz-executor4'. FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 1 CPU: 0 PID: 7850 Comm: syz-executor5 Not tainted 4.17.0-rc2+ #22 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+0x1b9/0x294 lib/dump_stack.c:113 fail_dump lib/fault-inject.c:51 [inline] should_fail.cold.4+0xa/0x1a lib/fault-inject.c:149 __should_failslab+0x124/0x180 mm/failslab.c:32 should_failslab+0x9/0x14 mm/slab_common.c:1522 slab_pre_alloc_hook mm/slab.h:423 [inline] slab_alloc_node mm/slab.c:3299 [inline] kmem_cache_alloc_node+0x272/0x780 mm/slab.c:3642 __alloc_skb+0x111/0x780 net/core/skbuff.c:193