From: Dennis Dalessandro <dennis.dalessandro@intel.com>
To: jgg@ziepe.ca, dledford@redhat.com
Cc: Mike Marciniszyn <mike.marciniszyn@intel.com>,
linux-rdma@vger.kernel.org,
Lukasz Odzioba <lukasz.odzioa@intel.com>,
stable@vger.kernel.org,
"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
Ira Weiny <ira.weiny@intel.com>
Subject: [PATCH for-next 0/4] IB/hfi1: Couple more for the RC cycle
Date: Thu, 20 Sep 2018 12:44:03 -0700 [thread overview]
Message-ID: <20180920193538.7072.71796.stgit@scvm10.sc.intel.com> (raw)
Hi Doug and Jason,
Mike and Ira have identified some fixes that they would like to see land in the
RC, these are serious problems and are marked as stable.
---
Ira Weiny (1):
IB/hfi1: Fix SL array bounds check
Michael J. Ruhl (3):
IB/hfi1: Invalid user input can result in crash
IB/hfi1: Fix context recovery when PBC has an UnsupportedVL
IB/hfi1: Fix destroy_qp hang after a link down
drivers/infiniband/hw/hfi1/chip.c | 6 +++-
drivers/infiniband/hw/hfi1/pio.c | 51 ++++++++++++++++++++++++++------
drivers/infiniband/hw/hfi1/pio.h | 2 +
drivers/infiniband/hw/hfi1/user_sdma.c | 2 +
drivers/infiniband/hw/hfi1/verbs.c | 8 ++++-
5 files changed, 56 insertions(+), 13 deletions(-)
next reply other threads:[~2018-09-20 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 19:44 Dennis Dalessandro [this message]
2018-09-20 19:44 ` [PATCH for-next 1/4] IB/hfi1: Fix SL array bounds check Dennis Dalessandro
2018-09-20 19:44 ` [PATCH for-next 2/4] IB/hfi1: Invalid user input can result in crash Dennis Dalessandro
2018-09-20 19:44 ` [PATCH for-next 3/4] IB/hfi1: Fix context recovery when PBC has an UnsupportedVL Dennis Dalessandro
2018-09-20 19:44 ` [PATCH for-next 4/4] IB/hfi1: Fix destroy_qp hang after a link down Dennis Dalessandro
2018-09-20 19:52 ` [PATCH for-next 0/4] IB/hfi1: Couple more for the RC cycle Dennis Dalessandro
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=20180920193538.7072.71796.stgit@scvm10.sc.intel.com \
--to=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=ira.weiny@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=lukasz.odzioa@intel.com \
--cc=michael.j.ruhl@intel.com \
--cc=mike.marciniszyn@intel.com \
--cc=stable@vger.kernel.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).