ice: fix incorrect dev_dbg print mistaking 'i' for vf->vf_id
authorJacob Keller <jacob.e.keller@intel.com>
Wed, 23 Feb 2022 00:27:00 +0000 (16:27 -0800)
committerTony Nguyen <anthony.l.nguyen@intel.com>
Tue, 15 Mar 2022 20:22:19 +0000 (13:22 -0700)
If we fail to clear the malicious VF indication after a VF reset, the
dev_dbg message which is printed uses the local variable 'i' when it
meant to use vf->vf_id. Fix this.

Fixes: 0891c89674e8 ("ice: warn about potentially malicious VFs")
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
drivers/net/ethernet/intel/ice/ice_sriov.c

index 2f74fcf51c2c2b33b97265eee537adf4f203f87f..91d106528b66e902d272ba54b0cee16e4bffb1eb 100644 (file)
@@ -1381,7 +1381,8 @@ bool ice_reset_vf(struct ice_vf *vf, bool is_vflr)
        /* if the VF has been reset allow it to come up again */
        if (ice_mbx_clear_malvf(&hw->mbx_snapshot, pf->vfs.malvfs,
                                ICE_MAX_SRIOV_VFS, vf->vf_id))
-               dev_dbg(dev, "failed to clear malicious VF state for VF %u\n", i);
+               dev_dbg(dev, "failed to clear malicious VF state for VF %u\n",
+                       vf->vf_id);
 
        return true;
 }