iavf: do not track VLAN 0 filters
authorAhmed Zaki <ahmed.zaki@intel.com>
Wed, 15 Mar 2023 19:59:25 +0000 (13:59 -0600)
committerTony Nguyen <anthony.l.nguyen@intel.com>
Thu, 16 Mar 2023 15:47:42 +0000 (08:47 -0700)
commit964290ff32d132bf971d45b29f7de39756dab7c8
treeadc70f4c7c01cd391d8a73d3c5c3f587c81eaa1a
parentde58647b4301fe181f9c38e8b46f7021584ae427
iavf: do not track VLAN 0 filters

When an interface with the maximum number of VLAN filters is brought up,
a spurious error is logged:

    [257.483082] 8021q: adding VLAN 0 to HW filter on device enp0s3
    [257.483094] iavf 0000:00:03.0 enp0s3: Max allowed VLAN filters 8. Remove existing VLANs or disable filtering via Ethtool if supported.

The VF driver complains that it cannot add the VLAN 0 filter.

On the other hand, the PF driver always adds VLAN 0 filter on VF
initialization. The VF does not need to ask the PF for that filter at
all.

Fix the error by not tracking VLAN 0 filters altogether. With that, the
check added by commit 0e710a3ffd0c ("iavf: Fix VF driver counting VLAN 0
filters") in iavf_virtchnl.c is useless and might be confusing if left as
it suggests that we track VLAN 0.

Fixes: 0e710a3ffd0c ("iavf: Fix VF driver counting VLAN 0 filters")
Signed-off-by: Ahmed Zaki <ahmed.zaki@intel.com>
Reviewed-by: Michal Kubiak <michal.kubiak@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
drivers/net/ethernet/intel/iavf/iavf_main.c
drivers/net/ethernet/intel/iavf/iavf_virtchnl.c