On Wed, May 24, 2017 at 07:58:17PM +0000, Majd Dibbiny wrote: > > > On May 24, 2017, at 10:19 PM, Jason Gunthorpe <jgunthorpe@xxxxxxxxxxxxxxxxxxxx> wrote: > > > >> On Wed, May 24, 2017 at 09:52:56PM +0300, Leon Romanovsky wrote: > >>> On Wed, May 24, 2017 at 10:38:32AM -0600, Jason Gunthorpe wrote: > >>>> On Sun, May 21, 2017 at 06:44:43PM +0300, Leon Romanovsky wrote: > >>>>> On Sun, May 21, 2017 at 02:30:04PM +0000, Parav Pandit wrote: > >>>>> Hi Sagi, > >>>>> > >>>>> Majd encountered same sometime back and reported [1]. > >>>>> He has the fix should be posting the fix soon. > >>>>> > >>>>> Majd/Leon? > >>>> > >>>> The fix is in our rdma-rc branch. > >>>> https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/commit/?h=rdma-rc&id=f1fff656d55c52aeb12129f57347886b02f90e1d > >>>> > >>>> I planned to submit it today. > >>> > >>> Is someone going to look at the segfault in librdmacm? > >> > >> Does it reproduce with these two patches? > > > > I don't think librdmacm should segfault even if the kernel is > > malfunctioning, should it? > The problem now is a kernel panic.. which segfault are you referring > to? The original report refered to a user space seg fault, is that just blowback from the kernel panic? Jason -- 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
