| commit | 326439883e17fca029f4ed05307480bdb6369877 | |
| author | Yuval Mintz <Yuval.Mintz@qlogic.com> | |
| Sun, 19 Jun 2016 12:18:12 +0000 (19 15:18 +0300) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Sun, 19 Jun 2016 17:47:32 +0000 (19 10:47 -0700) | ||
| tree | d504895703b1725f7c742f971e80ea139d1832e8 | treesnapshot (tar.gz zip) |
| parent | e6bd89232b4a4c9282da1ac8bdd798c2a30d9a46 | commitdiff |
qed: Prevent VF from Tx-switching 'promisc'
Internal loopback in driver is based on two things - first
is the willingness of transmitter to use it [in case of VFs,
this can be forced based on VEPA/VEB] and secondly on another
vport classification configuration which should match the
packet's destination.
Current code allows non-linux VFs to configure a 'promisc'
mode on Tx, meaning all traffic sent by VF would be loopbacked
internally by firmware; This isn't considered a valid mode and
as such should be prevented by PF.
Signed-off-by: Yuval Mintz <Yuval.Mintz@qlogic.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Internal loopback in driver is based on two things - first
is the willingness of transmitter to use it [in case of VFs,
this can be forced based on VEPA/VEB] and secondly on another
vport classification configuration which should match the
packet's destination.
Current code allows non-linux VFs to configure a 'promisc'
mode on Tx, meaning all traffic sent by VF would be loopbacked
internally by firmware; This isn't considered a valid mode and
as such should be prevented by PF.
Signed-off-by: Yuval Mintz <Yuval.Mintz@qlogic.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
| drivers/net/ethernet/qlogic/qed/qed_l2.c | diffblobblamehistory |