Juliet Kim f9c6cea0b3 ibmvnic: Skip fatal error reset after passive init ... During MTU change, the following events may happen. Client-driven CRQ initialization fails due to partner’s CRQ closed, causing client to enqueue a reset task for FATAL_ERROR. Then passive (server-driven) CRQ initialization succeeds, causing client to release CRQ and enqueue a reset task for failover. If the passive CRQ initialization occurs before the FATAL reset task is processed, the FATAL error reset task would try to access a CRQ message queue that was freed, causing an oops. The problem may be most likely to occur during DLPAR add vNIC with a non-default MTU, because the DLPAR process will automatically issue a change MTU request. Fix this by not processing fatal error reset if CRQ is passively initialized after client-driven CRQ initialization fails. Signed-off-by: Juliet Kim <julietk@linux.vnet.ibm.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2020-04-30 13:27:17 -07:00
..
ehea	netdev: pass the stuck queue to the timeout handler	2019-12-12 21:38:57 -08:00
emac	net: ibm: remove set but not used variables 'err'	2020-03-11 23:32:55 -07:00
ibmveth.c	ibmveth: Remove unused page_offset macro	2020-03-05 17:35:06 -08:00
ibmveth.h	net/ethtool: Introduce link_ksettings API for virtual network devices	2020-02-29 21:48:55 -08:00
ibmvnic.c	ibmvnic: Skip fatal error reset after passive init	2020-04-30 13:27:17 -07:00
ibmvnic.h	ibmvnic: Do not process device remove during device reset	2020-03-10 15:50:42 -07:00
Kconfig
Makefile