summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorJesse Brandeburg <jesse.brandeburg@intel.com>2015-11-18 15:47:06 -0800
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>2015-12-03 13:43:06 -0800
commit8ddb33268902c80ecd9a0e1bc766a2dc4bc9fede (patch)
treed01fe095c8d1511a4cc7abaca47f07532eca2839 /MAINTAINERS
parent6e80a18c561485b5168a94b2637ceefb0133d4b5 (diff)
downloadlinux-8ddb33268902c80ecd9a0e1bc766a2dc4bc9fede.tar.bz2
i40e/i40evf: avoid mutex re-init
If the driver were to happen to have a mutex held while the i40e_init_adminq call was called, the init_adminq might inadvertently call mutex_init on a lock that was held which is a violation of the calling semantics. Fix this by avoiding adminq.c code allocating/freeing this memory, and then do the same work only once in probe/remove. Testing Hints (Required if no HSD): for VF, load i40evf in bare metal and echo 32 > sriov_numvfs; echo 0 > sriov_numvfs in a loop. Yes this is a horrible thing to do. Change-ID: Ida263c51b34e195252179e7e5e400d73a99be7a2 Reported-by: Stefan Assmann <sassmann@redhat.com> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com> Tested-by: Andrew Bowers <andrewx.bowers@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions