Dave Jiang c1628774f0 ntb: transport shouldn't disable link due to bogus values in SPADs ... commit f3fd2afed8 upstream. It seems that under certain scenarios the SPAD can have bogus values caused by an agent (i.e. BIOS or other software) that is not the kernel driver, and that causes memory window setup failure. This should not cause the link to be disabled because if we do that, the driver will never recover again. We have verified in testing that this issue happens and prevents proper link recovery. Signed-off-by: Dave Jiang <dave.jiang@intel.com> Acked-by: Allen Hubbe <Allen.Hubbe@dell.com> Signed-off-by: Jon Mason <jdmason@kudzu.us> Fixes: 84f766855f ("ntb: stop link work when we do not have memory") Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2017-08-30 10:21:55 +02:00
..
hw	ntb: ntb_hw_intel: init peer_addr in struct intel_ntb_dev	2016-11-13 16:48:29 -05:00
test	ntb: ntb_perf missing dmaengine_unmap_put	2017-02-23 17:44:36 +01:00
Kconfig	NTB: Add ping pong test client	2015-07-04 14:07:42 -04:00
Makefile	NTB: Add ping pong test client	2015-07-04 14:07:42 -04:00
ntb.c	ntb: avoid format string in dev_set_name	2015-08-09 16:32:22 -04:00
ntb_transport.c	ntb: transport shouldn't disable link due to bogus values in SPADs	2017-08-30 10:21:55 +02:00