redonkable
/
remarkable-linux
1
0
Fork 0
Code Releases Activity

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>
steinar/wifi_calib_4_9_kernel
Dave Jiang 2017-07-28 15:10:48 -07:00 committed by Greg Kroah-Hartman
parent 4d4f35473d
commit c1628774f0
1 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
drivers/ntb/ntb_transport.c
View File

@ -921,10 +921,8 @@ out1:
ntb_free_mw(nt, i);
/* if there's an actual failure, we should just bail */
if (rc < 0) {
ntb_link_disable(ndev);
if (rc < 0)
return;
}
out:
if (ntb_link_is_up(ndev, NULL, NULL) == 1)