diff options
author | 2015-10-19 04:23:29 -0600 | |
---|---|---|
committer | 2015-12-12 23:19:37 -0800 | |
commit | be06998f96ecb93938ad2cce46c4289bf7cf45bc (patch) | |
tree | bf9734ce50b08ea653bfdce65119ee0c2f227fe0 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | e1000e: Increase timeout of polling bit RSPCIPHY (diff) | |
download | linux-dev-be06998f96ecb93938ad2cce46c4289bf7cf45bc.tar.xz linux-dev-be06998f96ecb93938ad2cce46c4289bf7cf45bc.zip |
igb: fix NULL derefs due to skipped SR-IOV enabling
The combined effect of commits 6423fc3416 ("igb: do not re-init SR-IOV
during probe") and ceee3450b3 ("igb: make sure SR-IOV init uses the
right number of queues") causes VFs no longer getting set up, leading
to NULL pointer dereferences due to the adapter's ->vf_data being NULL
while ->vfs_allocated_count is non-zero. The first commit not only
neglected the side effect of igb_sriov_reinit() that the second commit
tried to account for, but also that of setting IGB_FLAG_HAS_MSIX,
without which igb_enable_sriov() is effectively a no-op. Calling
igb_{,re}set_interrupt_capability() as done here seems to address this,
but I'm not sure whether this is better than sinply reverting the other
two commits.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Tested-by: Aaron Brown <aaron.f.brown@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions