From: Christoph Paasch <[email protected]> Date: Tue, 18 Feb 2014 14:06:57 +0100
> When igb_set_interrupt_capability() calls > igb_reset_interrupt_capability() (e.g., because CONFIG_PCI_MSI is unset), > num_q_vectors has been set but no vector has yet been allocated. > > igb_reset_interrupt_capability() will then call igb_reset_q_vector, > which assumes that the vector is allocated. As this is not the case, we > are accessing a NULL-pointer. > > This patch fixes it by checking that q_vector is indeed different from > NULL. > > Fixes: 02ef6e1d0b0023 (igb: Fix queue allocation method to accommodate > changing during runtime) > Cc: Carolyn Wyborny <[email protected]> > Signed-off-by: Christoph Paasch <[email protected]> Intel folks, please queue this up, thanks. ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
