Signed-off-by: Yishai Hadas yish...@mellanox.com
Signed-off-by: Tzahi Oved tza...@mellanox.com
---
changes from V3:
Use mlx4_device to wrap verbs_device instead of mlx4_device_ex
Use calloc instead of malloc as part of struct mlx4_device allocation
- 2 changes below are based on Jason's comment
This is a short series of fixes for minor issues. The most important
being a memcpy buffer overrun on ppc arch for the compatibility wrapper.
The rest are usability fixes for the example programs.
Doug Ledford (5):
Add an error when the user specifies an invalid port
Don't allow port == 0 as
Signed-off-by: Doug Ledford dledf...@redhat.com
---
examples/devinfo.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/examples/devinfo.c b/examples/devinfo.c
index 7dc0463..b1a3b2e 100644
--- a/examples/devinfo.c
+++ b/examples/devinfo.c
@@ -218,10 +218,16 @@
The physical link state on iWARP transports has no meaning, so
don't print it out at all.
Signed-off-by: Doug Ledford dledf...@redhat.com
---
examples/devinfo.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/examples/devinfo.c b/examples/devinfo.c
index
The ppc arch packs the work request struct 1.0 in such a way that
a straight memcpy won't work. Instead, break the copy out into
chunks whenever the sizes don't match for given portions of the
struct.
Found by built in gcc memcpy buffer overflow checks.
Help on the right fix provided by Jakub
We special case port == 0 to mean all ports, and it's the default,
so if a user passes in 0, they likely meant 1 instead. Throw an
error because they probably didn't mean to specify the default
behavior of scan all ports. Path of least surprise and all that.
Signed-off-by: Doug Ledford
The UD protocol doesn't support message sizes larger than the path
MTU. We don't go so far as to check path MTU, but we do check port
MTU. This prevents failed runs of the pingpong_ud program with large
MTUs.
Signed-off-by: Doug Ledford dledf...@redhat.com
---
examples/ud_pingpong.c | 14
