osm_vl15intf.c: fixing use-after-free coredump

p_madw is freed if responce is not expected. Signed-off-by: Yevgeny Kliteynik klit...@dev.mellanox.co.il --- opensm/opensm/osm_vl15intf.c |5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/opensm/opensm/osm_vl15intf.c b/opensm/opensm/osm_vl15intf.c index

[PATCH] Add exponential backoff + random delay to MADs when retrying after timeout.

This patch builds upon a discussion we had earlier this year on adding a backoff function when retrying MAD sends after a timeout. This patch does NOT implement the ABI/API changes that would be needed to take advantage of the new features, but it lays the groundwork for doing so. In addition,

[PATCH] Handling BUSY responses from the SM.

This patch builds upon feedback received earlier this year to add a treat BUSY as timeout feature to ib_mad. It does NOT implement the ABI/API changes that would be needed in user space to take advantage of the new feature, but it lays the groundwork for doing so. In addition, it provides a new

FW: Trying to link with DAT 2.0 function

Hello, I'm trying to create a shared library that uses the function dat_cno_fd_create(), but I find that I get an undefined symbol error when I compile a test executable which links with my shared library. Doing an nm on the libdat2.so I see that this function (along with csp_create, csp_query,

RE: Trying to link with DAT 2.0 function

I'm trying to create a shared library that uses the function dat_cno_fd_create(), but I find that I get an undefined symbol error when I compile a test executable which links with my shared library. Sorry, while this new call was defined in the DAT 2.0 specification, it has not yet been

RE: EXTERNAL:RE: Trying to link with DAT 2.0 function

Thanks for your response! I suspected that this might be the case... Do you have a roadmap available? Is this planned to be implemented in the near future? -Original Message- From: Davis, Arlin R [mailto:arlin.r.da...@intel.com] Sent: Monday, October 11, 2010 5:00 PM To: Young, Eric R.;

RE: Trying to link with DAT 2.0 function

Do you have a roadmap available? Is this planned to be implemented in the near future? There are no plans. I really don't know how this call even made it in the specification given that DAT is suppose to be O/S agnostic. In any case, can you use dat_cno_wait() on top of the EVD's as a means to

Re: [PATCH] mlx4: Limit num of fast reg WRs

thanks, applied (with s/MAX_FAST_REG_PAGES/MLX4_MAX_FAST_REG_PAGES/ to avoid namespace pollution). -- To unsubscribe from this list: send the line unsubscribe linux-rdma in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH] mlx4: Limit num of fast reg WRs

Eli Cohen e...@dev.mellanox.co.il wrote: Fix the limit of max fast regisreation WRs that can be posted to CX to match hardware capabilities. Guys, can you clarify if the hardware limitation is 511 entries or its (PAGE_SIZE / sizeof(pointer)) - 1 which is 4096 / 8 - 1 = 511 but can change if

Re: fixing blocking rdma_connect call on failure

Thanks, applied (with Steve Wise's ack-ed by). This patch was actually whitespace mangled (tabs turned to spaces) and so I had to apply it by hand. In the future please try to send patches with a mailer that does not mangle them, so that they can be handled automatically. - R. -- To

[RFC] IB/uverbs: Add support for passing memory region invalidations to userspace

Hi everyone, I think I've finally gotten my revision of ummunotify to live within userspace verbs into a reasonable state. I've done no testing beyond compiling it and reading over the code -- in fact, I haven't even implemented the corresponding support in libibverbs -- but I wanted to get this