summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorSteve Wise <swise@opengridcomputing.com>2015-05-07 16:34:23 -0500
committerDoug Ledford <dledford@redhat.com>2015-05-11 17:16:49 -0400
commit940fd304d233534038365f56d30c29ed7fd7416b (patch)
tree31f265af917a9931d035dc627c07a6b80bd544ab /arch
parent94634e9861abbc3036d7041773971c8e31ec2680 (diff)
downloadtalos-op-linux-940fd304d233534038365f56d30c29ed7fd7416b.tar.gz
talos-op-linux-940fd304d233534038365f56d30c29ed7fd7416b.zip
iw_cxgb4: use wildcard mapping for getting remote addr info
For listening endpoints bound to the wildcard address, we need to pass the wildcard address mapping to iwpm_get_remote_info() instead of the mapped address of the new child connection. Without this fix, and with iwarp port mapping enabled, each iw_cxgb4 connection that is spawned from a listening endpoint bound to the wildcard address, will generate an annoying dmesg entry about failing to find the remote address mapping info, and the connection state displayed in debugfs under /sys/kernel/debug/iw_cxgb4/<pci-slot-no>/eps will not have the peer's address/port mapping info. The connection still works though. Fixes: 5b6b8fe ("RDMA/cxgb4: Report the actual address of the remote connecting peer") Signed-off-by: Steve Wise <swise@opengridcomputing.com> Reviewed-by: Tatyana Nikolova <Tatyana.E.Nikolova@intel.com> Reviewed-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> Signed-off-by: Doug Ledford <dledford@redhat.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud