On Wed, May 24, 2017 at 3:13 PM, Hefty, Sean <sean.hefty@xxxxxxxxx> wrote: >> The original report refered to a user space seg fault, is that just >> blowback from the kernel panic? > > I think it was rping that was seg faulting, not librdmacm. If this is in regard to "rdma_cm segfaults on RoCE with ConnectX-4 [WAS: Re: rping segfault with 4.9.28 on CentOS 7.3]", I think we have narrowed it down to the node GUID being '0' or something along those lines. We are still digging into it. We are not getting a kernel backtrace when librdmacm segfaults. ---------------- Robert LeBlanc PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1 -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
