aboutsummaryrefslogtreecommitdiffstats
path: root/net/sched/sch_generic.c
diff options
context:
space:
mode:
authorJacob Keller <jacob.e.keller@intel.com>2016-03-31 09:52:30 -0700
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>2016-04-13 20:06:55 -0700
commitf808c5dbcdc393be8e9f676c61baac6a3db382c1 (patch)
treec7ecff5bab3471fb8a95d93b07ed6e59ccf48711 /net/sched/sch_generic.c
parenti40e/i40evf: Limit TSO to 7 descriptors for payload instead of 8 per packet (diff)
downloadlinux-dev-f808c5dbcdc393be8e9f676c61baac6a3db382c1.tar.xz
linux-dev-f808c5dbcdc393be8e9f676c61baac6a3db382c1.zip
fm10k: fix multi-bit VLAN update requests from VF
The VF uses a multi-bit update request to clear unused VLANs whenever it resets. However, an accident in a previous refector broke multi-bit updates for VFs, due to misreading a comment in fm10k_vf.c and attempting to reduce code duplication. The problem occurs because a multi-bit request has a non-zero length, and the PF would simply drop any request with the upper 16 bits set. We can't simply remove the check of the upper 16 bits and the call to fm10k_iov_select vid, because this would remove the checks for default VID and for ensuring no other VLANs can be enabled except pf_vid when it has been set. To resolve that issue, this revision uses the iov_select_vid when we have a single-bit update, and denies any multi-bit update when the VLAN was administratively set by the PF. This should be ok since the PF properly updates VLAN_TABLE when it assigns the PF vid. This ensures that requests to add or remove the PF vid work as expected, but a rogue VF could not use the multi-bit update as a loophole to attempt receiving traffic on other VLANs. Reported-by: Ngai-Mint Kwan <ngai-mint.kwan@intel.com> Signed-off-by: Jacob Keller <jacob.e.keller@intel.com> Tested-by: Krishneil Singh <Krishneil.k.singh@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'net/sched/sch_generic.c')
0 files changed, 0 insertions, 0 deletions