INIT: Entering runlevel: 2 [info] Using makefile-style concurrent boot in runlevel 2. [....] Starting enhanced syslogd: rsyslogd[?25l[?1c7[ ok 8[?25h[?0c. [....] Starting periodic command scheduler: cron[?25l[?1c7[ ok 8[?25h[?0c. [....] Starting OpenBSD Secure Shell server: sshd[?25l[?1c7[ ok 8[?25h[?0c. Debian GNU/Linux 7 syzkaller ttyS0 Warning: Permanently added '10.128.10.16' (ECDSA) to the list of known hosts. 2018/04/19 13:41:30 fuzzer started 2018/04/19 13:41:30 connecting to host at 10.128.0.26:40315 2018/04/19 13:41:30 checking config... syzkaller login: [ 49.212930] can: request_module (can-proto-0) failed. [ 49.222118] can: request_module (can-proto-0) failed. 2018/04/19 13:41:50 enabled syscalls: 654 2018/04/19 13:41:50 testing simple program... [ 50.636456] IPVS: ftp: loaded support on port[0] = 21 [ 50.959803] bridge0: port 1(bridge_slave_0) entered blocking state [ 50.966272] bridge0: port 1(bridge_slave_0) entered disabled state [ 50.973781] device bridge_slave_0 entered promiscuous mode [ 50.997653] bridge0: port 2(bridge_slave_1) entered blocking state [ 51.004064] bridge0: port 2(bridge_slave_1) entered disabled state [ 51.011622] device bridge_slave_1 entered promiscuous mode [ 51.034836] IPv6: ADDRCONF(NETDEV_UP): veth0_to_bridge: link is not ready [ 51.059668] IPv6: ADDRCONF(NETDEV_UP): veth1_to_bridge: link is not ready [ 51.123508] bond0: Enslaving bond_slave_0 as an active interface with an up link [ 51.150219] bond0: Enslaving bond_slave_1 as an active interface with an up link [ 51.251624] IPv6: ADDRCONF(NETDEV_UP): team_slave_0: link is not ready [ 51.258905] team0: Port device team_slave_0 added [ 51.281895] IPv6: ADDRCONF(NETDEV_UP): team_slave_1: link is not ready [ 51.289007] team0: Port device team_slave_1 added [ 51.312514] IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_0: link becomes ready [ 51.338503] IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_1: link becomes ready [ 51.363918] IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_bridge: link becomes ready [ 51.389647] IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_bridge: link becomes ready [ 51.597346] bridge0: port 2(bridge_slave_1) entered blocking state [ 51.603806] bridge0: port 2(bridge_slave_1) entered forwarding state [ 51.610775] bridge0: port 1(bridge_slave_0) entered blocking state [ 51.617138] bridge0: port 1(bridge_slave_0) entered forwarding state [ 52.351751] 8021q: adding VLAN 0 to HW filter on device bond0 [ 52.424399] IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready [ 52.495506] IPv6: ADDRCONF(NETDEV_UP): veth1: link is not ready [ 52.501677] IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready [ 52.509148] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready [ 52.578220] 8021q: adding VLAN 0 to HW filter on device team0 2018/04/19 13:41:52 execution failed: executor 0: failed: net.ipv6.conf.syz_tun.accept_dad = 0 net.ipv6.conf.syz_tun.router_solicitations = 0 RTNETLINK answers: Operation not supported RTNETLINK answers: No buffer space available RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Invalid argument RTNETLINK answers: Invalid argument RTNETLINK answers: Invalid argument getsockopt(EBT_SO_GET_INIT_ENTRIES) (errno 22) loop failed (errno 0) net.ipv6.conf.syz_tun.accept_dad = 0 net.ipv6.conf.syz_tun.router_solicitations = 0 RTNETLINK answers: Operation not supported RTNETLINK answers: No buffer space available RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Invalid argument RTNETLINK answers: Invalid argument RTNETLINK answers: Invalid argument getsockopt(EBT_SO_GET_INIT_ENTRIES) (errno 22) loop failed (errno 0)