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.0.32' (ECDSA) to the list of known hosts. 2018/04/13 20:53:26 fuzzer started 2018/04/13 20:53:27 connecting to host at 10.128.0.26:36021 2018/04/13 20:53:27 checking config... syzkaller login: [ 34.603568] can: request_module (can-proto-0) failed. [ 34.612960] can: request_module (can-proto-0) failed. 2018/04/13 20:53:30 enabled syscalls: 1624 2018/04/13 20:53:30 testing simple program... [ 35.163280] IPVS: ftp: loaded support on port[0] = 21 [ 35.500818] bridge0: port 1(bridge_slave_0) entered blocking state [ 35.507302] bridge0: port 1(bridge_slave_0) entered disabled state [ 35.514693] device bridge_slave_0 entered promiscuous mode [ 35.539185] bridge0: port 2(bridge_slave_1) entered blocking state [ 35.545565] bridge0: port 2(bridge_slave_1) entered disabled state [ 35.552710] device bridge_slave_1 entered promiscuous mode [ 35.576152] IPv6: ADDRCONF(NETDEV_UP): veth0_to_bridge: link is not ready [ 35.601536] IPv6: ADDRCONF(NETDEV_UP): veth1_to_bridge: link is not ready [ 35.670463] bond0: Enslaving bond_slave_0 as an active interface with an up link [ 35.696932] bond0: Enslaving bond_slave_1 as an active interface with an up link [ 35.800349] IPv6: ADDRCONF(NETDEV_UP): team_slave_0: link is not ready [ 35.807714] team0: Port device team_slave_0 added [ 35.830820] IPv6: ADDRCONF(NETDEV_UP): team_slave_1: link is not ready [ 35.837945] team0: Port device team_slave_1 added [ 35.861555] IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_0: link becomes ready [ 35.889421] IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_1: link becomes ready [ 35.915142] IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_bridge: link becomes ready [ 35.941830] IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_bridge: link becomes ready [ 36.160582] bridge0: port 2(bridge_slave_1) entered blocking state [ 36.167068] bridge0: port 2(bridge_slave_1) entered forwarding state [ 36.174062] bridge0: port 1(bridge_slave_0) entered blocking state [ 36.180427] bridge0: port 1(bridge_slave_0) entered forwarding state [ 36.966964] 8021q: adding VLAN 0 to HW filter on device bond0 [ 37.042769] IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready [ 37.118312] IPv6: ADDRCONF(NETDEV_UP): veth1: link is not ready [ 37.124485] IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready [ 37.131714] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready [ 37.203401] 8021q: adding VLAN 0 to HW filter on device team0 2018/04/13 20:53:33 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)