ice_vc_vali..._setting_msg(9)
π ice_vc_valid_vlan_setting_msg(9) β Kernel API Manual, but make it make sense
okay so bestie, welcome to the <purple>Kernel API Manual</purple> β¨ this little page is all about ice_vc_valid_vlan_setting_msg, and yes the header truncated the name because apparently even manpage titles have a character limit π anyway let's go π«Ά
β¨ NAME β¨
ice_vc_valid_vlan_setting_msg β validate the VLAN setting message π
π SYNOPSIS π
bool ice_vc_valid_vlan_setting_msg (struct virtchnl_vlan_supported_caps
*caps , struct virtchnl_vlan_setting *msg );
so it hands back a bool, takes two pointers, and that's literally the whole vibe check πΈ
π¦ ARGUMENTS π¦
capsβ the negotiated VLAN settings from during VF init, like the receipts of what got agreed on earlier πmsgβ the message that needs validating, aka the one on trial π₯
π DESCRIPTION π
okay so picture this: this function is the bouncer at the club π§ it's used to validate any VLAN virtchnl message that shows up dressed as a virtchnl_vlan_setting structure.
it checks the message against the caps that were negotiated/supported during VF driver init β like, "girl, were you even on the guest list?" π if it matches, slay. if not, no entry β¨
π SEE ALSO π
and now for the friend group, the whole entire squad, no one left out fr fr π
first up, the source file:
Kernel file ./drivers/net/ethernet/intel/ice/virt/virtchnl.c
then the icons themselves:
ice_vc_vf_broadcast(9)ice_set_pfe_link(9)ice_vc_notify_vf_link_state(9)ice_vc_notify_link_state(9)ice_vc_notify_reset(9)ice_vc_send_msg_to_vf(9)ice_vc_get_ver_msg(9)ice_vc_get_vlan_caps(9)ice_vc_get_vf_res_msg(9)ice_vc_reset_vf_msg(9)ice_vc_isvalid_vsi_id(9)ice_vc_get_qos_caps(9)ice_vc_cfg_promiscuous_mode_msg(9)ice_vc_get_stats_msg(9)ice_can_vf_change_mac(9)ice_vc_ether_addr_type(9)ice_is_vc_addr_legacy(9)ice_is_vc_addr_primary(9)ice_vfhw_mac_add(9)ice_is_mc_lldp_eth_addr(9)ice_vc_can_add_mac(9)ice_vc_add_mac_addr(9)ice_is_legacy_umac_expired(9)ice_update_legacy_cached_mac(9)ice_vfhw_mac_del(9)ice_vc_del_mac_addr(9)ice_vc_handle_mac_addr_msg(9)ice_vc_add_mac_addr_msg(9)ice_vc_del_mac_addr_msg(9)ice_vf_vlan_offload_ena(9)ice_is_vlan_promisc_allowed(9)ice_vf_ena_vlan_promisc(9)ice_vf_dis_vlan_promisc(9)ice_vf_has_max_vlans(9)ice_vc_process_vlan_msg(9)ice_vc_add_vlan_msg(9)ice_vc_remove_vlan_msg(9)ice_vsi_is_rxq_crc_strip_dis(9)ice_vc_ena_vlan_stripping(9)ice_vc_dis_vlan_stripping(9)ice_vc_query_rxdid(9)ice_vf_init_vlan_stripping(9)ice_vf_outer_vlan_not_allowed(9)ice_vc_set_dvm_caps(9)ice_vc_set_svm_caps(9)ice_vc_get_offload_vlan_v2_caps(9)ice_vc_validate_vlan_tpid(9)ice_vc_is_valid_vlan(9)ice_vc_validate_vlan_filter_list(9)ice_vc_to_vlan(9)ice_vc_vlan_action(9)ice_vc_del_vlans(9)ice_vc_remove_vlan_v2_msg(9)ice_vc_add_vlans(9)ice_vc_validate_add_vlan_filter_list(9)ice_vc_add_vlan_v2_msg(9)ice_vc_valid_vlan_setting(9)ice_vc_get_tpid(9)ice_vc_ena_vlan_offload(9)ice_vc_ena_vlan_stripping_v2_msg(9)ice_vc_dis_vlan_stripping_v2_msg(9)ice_vc_ena_vlan_insertion_v2_msg(9)ice_vc_dis_vlan_insertion_v2_msg(9)ice_virtchnl_set_dflt_ops(9)ice_vc_repr_add_mac(9)ice_vc_repr_del_mac(9)ice_virtchnl_set_repr_ops(9)ice_is_malicious_vf(9)ice_vc_process_vf_msg(9)
like I said β the whole squad, every single one, nobody gets left on read π€π
and that's the page!! π this cutie lives at ./drivers/net/ethernet/intel/i... (yes the path got truncated too, the terminal is doing its best π), dated October 2026, and it's filed under ice_vc_vali..._setting_msg(9) β okay bye bestie, go validate those messages, periodt π
β¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms