Logan Gunthorpe 33d353db12 ntb_transport: Fix bug with max_mw_size parameter ... [ Upstream commit cbd27448fa ] When using the max_mw_size parameter of ntb_transport to limit the size of the Memory windows, communication cannot be established and the queues freeze. This is because the mw_size that's reported to the peer is correctly limited but the size used locally is not. So the MW is initialized with a buffer smaller than the window but the TX side is using the full window. This means the TX side will be writing to a region of the window that points nowhere. This is easily fixed by applying the same limit to tx_size in ntb_transport_init_queue(). Fixes: e26a5843f7 ("NTB: Split ntb_hw_intel and ntb_transport drivers") Signed-off-by: Logan Gunthorpe <logang@deltatee.com> Acked-by: Allen Hubbe <Allen.Hubbe@dell.com> Cc: Dave Jiang <dave.jiang@intel.com> Signed-off-by: Jon Mason <jdmason@kudzu.us> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2018-05-30 07:50:22 +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_transport.c	ntb_transport: Fix bug with max_mw_size parameter	2018-05-30 07:50:22 +02:00
ntb.c	ntb: avoid format string in dev_set_name	2015-08-09 16:32:22 -04:00