From: Greg KH <greg@kroah.com>
To: Mustafa Ismail <mustafa.ismail@intel.com>
Cc: linux-rdma@vger.kernel.org, e1000-rdma@lists.sourceforge.net,
chien.tin.tung@intel.com, shiraz.saleem@intel.com,
"# v4 . 2-v4 . 9" <stable@vger.kernel.org>,
security@kernel.org, Doug Ledford <dledford@redhat.com>,
Steve Wise <swise@opengridcomputing.com>,
Mike Marciniszyn <mike.marciniszyn@intel.com>
Subject: Re: [PATCH] RDMA/uverbs: Fix the check for port number
Date: Thu, 3 Aug 2017 15:41:49 -0700 [thread overview]
Message-ID: <20170803224149.GF2396@kroah.com> (raw)
In-Reply-To: <1501085686-12916-1-git-send-email-mustafa.ismail@intel.com>
On Wed, Jul 26, 2017 at 11:14:46AM -0500, Mustafa Ismail wrote:
> 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> # v4.2-v4.9
> Cc: <security@kernel.org>
> Cc: Doug Ledford <dledford@redhat.com>
> Cc: Steve Wise <swise@opengridcomputing.com>
> Cc: Mike Marciniszyn <mike.marciniszyn@intel.com>
>
> Signed-off-by: Mustafa Ismail <mustafa.ismail@intel.com>
>
> Upstream commit 5a7a88f1b488("Fix the check for port number")
> Modified from upstream commit: helper function rdma_is_port_valid does not
> exist in these kernel versions.
Note, you sent this 3 times for some reason, why?
Also, it was hard to figure out what to do with it, I think it was ment
for me to apply to the 4.4 and 4.9-stable trees, right? If so, I've
done that, if not, please let me know.
thanks,
greg k-h
next prev parent reply other threads:[~2017-08-03 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 16:14 [PATCH] RDMA/uverbs: Fix the check for port number Mustafa Ismail
2017-08-03 22:41 ` Greg KH [this message]
2017-08-03 23:34 ` Saleem, Shiraz
2017-08-07 11:03 ` Yuval Shaia
2017-08-07 12:11 ` Chien Tin Tung
-- strict thread matches above, loose matches on Subject: below --
2017-07-26 15:18 Mustafa Ismail
2017-07-26 15:14 Mustafa Ismail
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=20170803224149.GF2396@kroah.com \
--to=greg@kroah.com \
--cc=chien.tin.tung@intel.com \
--cc=dledford@redhat.com \
--cc=e1000-rdma@lists.sourceforge.net \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=mustafa.ismail@intel.com \
--cc=security@kernel.org \
--cc=shiraz.saleem@intel.com \
--cc=stable@vger.kernel.org \
--cc=swise@opengridcomputing.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;
as well as URLs for NNTP newsgroup(s).