You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
any_test.go:65: generated too few complex types: 1060/1611
Mostly it failed to generate the autogenerated types, e.g.
any_test.go:61: did not generate netlink_msg_t[autogenerated_netlink, genlmsghdr, fw_policy$auto_cls_fw]
any_test.go:61: did not generate netlink_msg_t[autogenerated_netlink, genlmsghdr, nft_bitwise_policy$auto_nft_bitwise]
any_test.go:61: did not generate netlink_msg_t[autogenerated_netlink, genlmsghdr, nft_match_policy$auto_nft_compat]
any_test.go:61: did not generate netlink_msg_t[autogenerated_netlink, genlmsghdr, dcbnl_bcn_nest$auto_dcbnl]
any_test.go:61: did not generate netlink_msg_t[autogenerated_netlink, genlmsghdr, devlink_dl_port_function_nl_policy$auto_netlink_gen]
any_test.go:61: did not generate netlink_msg_t[autogenerated_netlink, genlmsghdr, ifa_phonet_policy$auto_pn_netlink]
any_test.go:61: did not generate netlink_msg_t[autogenerated_netlink, genlmsghdr, vni_filter_policy$auto_vxlan_vnifilter]
These types are effectively unused, we only reference then in the sendmsg$autorun syscall only to prevent unused warnings. It references dozens on policies, so there is no chance to generate them all in 10 attempts.
I think the proper fix is to not generate these unused policies (for now, while they are not used for real).
A hacky fix is to not test auto-generated ones, or special case sendmsg$autorun or auto_union.
I think the proper fix is to not generate these unused policies (for now, while they are not used for real).
do we actually still need sendmsg$autorun?
The only benefit in keeping unused policies is that it makes it more obvious how syz-declextract descriptions change over time, and might help in catching bugs between different versions. Other than that, I do not see any need to keep them.
Mostly it failed to generate the autogenerated types, e.g.
Cc @dvyukov
The text was updated successfully, but these errors were encountered: