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.49' (ECDSA) to the list of known hosts. 2018/04/21 18:05:09 fuzzer started 2018/04/21 18:05:10 connecting to host at 10.128.0.26:36021 2018/04/21 18:05:10 checking config... syzkaller login: [ 50.189929] can: request_module (can-proto-0) failed. [ 50.199196] can: request_module (can-proto-0) failed. 2018/04/21 18:05:31 enabled syscalls: 1625 2018/04/21 18:05:31 testing simple program... [ 51.794876] IPVS: ftp: loaded support on port[0] = 21 [ 52.118431] bridge0: port 1(bridge_slave_0) entered blocking state [ 52.124880] bridge0: port 1(bridge_slave_0) entered disabled state [ 52.132276] device bridge_slave_0 entered promiscuous mode [ 52.156966] bridge0: port 2(bridge_slave_1) entered blocking state [ 52.163359] bridge0: port 2(bridge_slave_1) entered disabled state [ 52.170479] device bridge_slave_1 entered promiscuous mode [ 52.193629] IPv6: ADDRCONF(NETDEV_UP): veth0_to_bridge: link is not ready [ 52.217783] IPv6: ADDRCONF(NETDEV_UP): veth1_to_bridge: link is not ready [ 52.281319] bond0: Enslaving bond_slave_0 as an active interface with an up link [ 52.306486] bond0: Enslaving bond_slave_1 as an active interface with an up link [ 52.407706] IPv6: ADDRCONF(NETDEV_UP): team_slave_0: link is not ready [ 52.414943] team0: Port device team_slave_0 added [ 52.438059] IPv6: ADDRCONF(NETDEV_UP): team_slave_1: link is not ready [ 52.445257] team0: Port device team_slave_1 added [ 52.468668] IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_0: link becomes ready [ 52.493638] IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_1: link becomes ready [ 52.518909] IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_bridge: link becomes ready [ 52.543888] IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_bridge: link becomes ready [ 52.745268] bridge0: port 2(bridge_slave_1) entered blocking state [ 52.751711] bridge0: port 2(bridge_slave_1) entered forwarding state [ 52.758636] bridge0: port 1(bridge_slave_0) entered blocking state [ 52.765043] bridge0: port 1(bridge_slave_0) entered forwarding state [ 53.533964] 8021q: adding VLAN 0 to HW filter on device bond0 [ 53.607851] IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready [ 53.680331] IPv6: ADDRCONF(NETDEV_UP): veth1: link is not ready [ 53.686495] IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready [ 53.693712] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready [ 53.763918] 8021q: adding VLAN 0 to HW filter on device team0 2018/04/21 18:05: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)