On Fri, 2013-03-01 at 11:42 +0800, xunleer wrote: > When the ixgbevf driver is opened the request to allocate MSIX irq > vectors may fail. In that case the driver will call ixgbevf_down() > which will call ixgbevf_irq_disable() to clear the HW interrupt > registers and calls synchronize_irq() using the msix_entries pointer > in > the adapter structure. However, when the function to request the MSIX > irq vectors failed it had already freed the msix_entries which causes > an OOPs from using the NULL pointer in synchronize_irq(). > > The calls to pci_disable_msix() and to free the msix_entries memory > should not occur if device open fails. Instead they should be called > during device driver removal to balance with the call to > pci_enable_msix() and the call to allocate msix_entries memory > during the device probe and driver load. > > Signed-off-by: Li Xun <xunleer...@huawei.com> > --- > drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 3 --- > 1 file changed, 3 deletions(-)
Updated the patch in my queue to this latest version.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
