From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Matan Barak <matanb@dev.mellanox.co.il>,
Matan Barak <matanb@mellanox.com>,
Yishai Hadas <yishaih@mellanox.com>,
Doug Ledford <dledford@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
Stephen Bates <sbates@raithlin.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Potnuri Bharat Teja <bharat@chelsio.com>
Subject: Re: BUG: NULL pointer dereference at ib_uverbs_comp_handler+0x20
Date: Tue, 1 Aug 2017 13:29:07 -0600 [thread overview]
Message-ID: <20170801192907.GB31205@obsidianresearch.com> (raw)
In-Reply-To: <5866fa2e-d3d9-cdaf-bcb4-806f938aef83@deltatee.com>
On Tue, Aug 01, 2017 at 12:32:57PM -0600, Logan Gunthorpe wrote:
> Couldn't create rdma QP - Invalid argument
> Unable to create QP.
> Failed to create QP.
Failing to create a QP makes me wonder if you have have this patch?
Subject: [PATCH v2 1/2] RDMA/uverbs: Fix the check for port number
The port number is only valid if IB_QP_PORT is set in the mask.
So only check port number if it is valid to prevent modify_qp from
failing due to an invalid port number.
Fixes: 5ecce4c9b17b("Check port number supplied by user verbs cmds")
Cc: <stable@vger.kernel.org> # v2.6.14+
Reviewed-by: Steve Wise <swise@opengridcomputing.com>
Signed-off-by: Mustafa Ismail <mustafa.ismail@intel.com>
Jason
next prev parent reply other threads:[~2017-08-01 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 17:38 BUG: NULL pointer dereference at ib_uverbs_comp_handler+0x20 Logan Gunthorpe
2017-08-01 11:08 ` Matan Barak
2017-08-01 12:30 ` Potnuri Bharat Teja
2017-08-01 18:35 ` Logan Gunthorpe
2017-08-01 18:32 ` Logan Gunthorpe
2017-08-01 19:29 ` Jason Gunthorpe [this message]
2017-08-01 19:39 ` Logan Gunthorpe
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=20170801192907.GB31205@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=bharat@chelsio.com \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=matanb@dev.mellanox.co.il \
--cc=matanb@mellanox.com \
--cc=sbates@raithlin.com \
--cc=sean.hefty@intel.com \
--cc=yishaih@mellanox.com \
/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