From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Parav Pandit <parav-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: rdma_cm NULL deref in 4.11.0+
Date: Wed, 24 May 2017 10:38:32 -0600 [thread overview]
Message-ID: <20170524163832.GA23034@obsidianresearch.com> (raw)
In-Reply-To: <20170521154443.GD17751-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
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?
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-24 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 13:59 rdma_cm NULL deref in 4.11.0+ Sagi Grimberg
[not found] ` <acc72471-eb22-4474-04f5-db23227faadd-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-05-21 14:30 ` Parav Pandit
[not found] ` <VI1PR0502MB30083E6CB505CA90A9E047C0D1FB0-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-05-21 15:44 ` Leon Romanovsky
[not found] ` <20170521154443.GD17751-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-05-24 16:38 ` Jason Gunthorpe [this message]
[not found] ` <20170524163832.GA23034-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-05-24 18:52 ` Leon Romanovsky
[not found] ` <20170524185256.GT17751-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-05-24 19:19 ` Jason Gunthorpe
[not found] ` <20170524191900.GA25200-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-05-24 19:58 ` Majd Dibbiny
[not found] ` <F8149B59-E43D-4E54-A901-1351BED23946-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-05-24 20:40 ` Jason Gunthorpe
[not found] ` <20170524204000.GA30878-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-05-24 21:13 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373AB120B2E-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-05-24 21:21 ` Robert LeBlanc
[not found] ` <CAANLjFqb7CGJOu_T4_PhuJLOsX0mxTo6SO_R67daRHKpnMFdvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-24 21:37 ` Hefty, Sean
[not found] ` <47078d0f-dc39-4a34-b641-0348877ca718@googlegroups.com>
[not found] ` <47078d0f-dc39-4a34-b641-0348877ca718-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-05-29 5:27 ` Leon Romanovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170524163832.GA23034@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=parav-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).