diff options
author | Jacob Keller | 2018-03-08 14:52:11 -0800 |
---|---|---|
committer | Jeff Kirsher | 2018-03-14 12:34:35 -0700 |
commit | 089915f0f23f1a09b4aecebe88212c5a4fef37fa (patch) | |
tree | e3c2ce6aa25ff5e4ed4b6a2312efecea74645cb1 /drivers/net/ethernet/qualcomm/qca_spi.c | |
parent | bc2a3a6cdb00c7e3c04735370fb5777d3cae22d2 (diff) |
i40e: restore TCPv4 input set when re-enabling ATR
When we re-enable ATR we need to restore the input set for TCPv4
filters, in order for ATR to function correctly. We already do this for
the normal case of re-enabling ATR when disabling ntuple support.
However, when re-enabling ATR after the last TCPv4 filter is removed (but
when ntuple support is still active), we did not restore the TCPv4
filter input set.
This can cause problems if the TCPv4 filters from FDir had changed the
input set, as ATR will no longer behave as expected.
When clearing the ATR auto-disable flag, make sure we restore the TCPv4
input set to avoid this.
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'drivers/net/ethernet/qualcomm/qca_spi.c')
0 files changed, 0 insertions, 0 deletions