linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: "Torvalds, Linus" <torvalds@linux-foundation.org>
Cc: "Gunthorpe, Jason" <jgg@ziepe.ca>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PULL REQUEST] Please pull rdma.git
Date: Fri, 02 Aug 2019 10:39:04 -0400	[thread overview]
Message-ID: <b64700fda3cd5c3cc19d6bf17c948b63a0413645.camel@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3191 bytes --]

Hi Linus,

Here's our second -rc pull request.  Nothing particularly special in
this one.  The client removal deadlock fix is kindy tricky, but we had
multiple eyes on it and no one could find a fault in it.  A couple
Spectre V1 fixes too.  Otherwise, all just normal -rc fodder.

Here's the boilerplate:

The following changes since commit b7165bd0d6cbb93732559be6ea8774653b204480:

  IB/mlx5: Fix RSS Toeplitz setup to be aligned with the HW specification (2019-07-25 11:45:48 -0300)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags/for-linus

for you to fetch changes up to 020fb3bebc224dfe9353a56ecbe2d5fac499dffc:

  RDMA/hns: Fix error return code in hns_roce_v1_rsv_lp_qp() (2019-08-01 12:53:53 -0400)

----------------------------------------------------------------
Pull request for 5.3-rc2

- A couple Spectre V1 fixes (umad, hfi1)
- Fix a tricky deadlock in the rdma core code with refcounting instead
  of locks (client removal patches)
- Build errors (hns)
- Fix a scheduling while atomic issue (mlx5)
- Use after free fix (mad)
- Fix error path return code (hns)
- Null deref fix (siw_crypto_hash)
- A few other misc. minor fixes

----------------------------------------------------------------
Bernard Metzler (1):
      Do not dereference 'siw_crypto_shash' before checking

Gal Pressman (1):
      RDMA/restrack: Track driver QP types in resource tracker

Gustavo A. R. Silva (1):
      IB/hfi1: Fix Spectre v1 vulnerability

Guy Levi (1):
      IB/mlx5: Fix MR registration flow to use UMR properly

Jack Morgenstein (1):
      IB/mad: Fix use-after-free in ib mad completion handling

Jason Gunthorpe (2):
      RDMA/devices: Do not deadlock during client removal
      RDMA/devices: Remove the lock around remove_client_context

Leon Romanovsky (1):
      RDMA/mlx5: Release locks during notifier unregister

Michal Kalderon (1):
      RDMA/qedr: Fix the hca_type and hca_rev returned in device attributes

Tony Luck (1):
      IB/core: Add mitigation for Spectre V1

Wei Yongjun (1):
      RDMA/hns: Fix error return code in hns_roce_v1_rsv_lp_qp()

YueHaibing (1):
      RDMA/hns: Fix build error

 drivers/infiniband/core/core_priv.h        |   5 +-
 drivers/infiniband/core/device.c           | 102 +++++++++++++++++++----------
 drivers/infiniband/core/mad.c              |  20 +++---
 drivers/infiniband/core/user_mad.c         |   6 +-
 drivers/infiniband/hw/hfi1/verbs.c         |   2 +
 drivers/infiniband/hw/hns/Kconfig          |   6 +-
 drivers/infiniband/hw/hns/Makefile         |   8 +--
 drivers/infiniband/hw/hns/hns_roce_hw_v1.c |   4 +-
 drivers/infiniband/hw/mlx5/main.c          |   7 +-
 drivers/infiniband/hw/mlx5/mr.c            |  27 +++-----
 drivers/infiniband/hw/qedr/main.c          |  10 ++-
 drivers/infiniband/sw/siw/siw_qp.c         |   6 +-
 include/rdma/ib_verbs.h                    |   4 +-
 13 files changed, 124 insertions(+), 83 deletions(-)

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-08-02 14:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 14:39 Doug Ledford [this message]
2019-08-02 22:10 ` [PULL REQUEST] Please pull rdma.git pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2019-08-30 15:42 Doug Ledford
2019-08-30 16:40 ` pr-tracker-bot
     [not found] <5b0aa103f6007e1887f9b2cacaec8015834589b8.camel@xsintricity.com>
2019-08-23 19:14 ` Doug Ledford
2019-08-14 14:59 Doug Ledford
2019-08-14 18:25 ` pr-tracker-bot
2019-08-19 10:08 ` Geert Uytterhoeven
2019-08-19 12:14   ` Jason Gunthorpe
2019-08-19 12:29     ` Geert Uytterhoeven
2019-08-19 12:48       ` Jason Gunthorpe
2019-06-21 19:42 Doug Ledford
2019-06-21 22:35 ` pr-tracker-bot
2018-12-13 16:56 Doug Ledford
2018-12-13 21:15 ` pr-tracker-bot
     [not found] <58466423-c87e-3921-101e-bffab8989fd8@redhat.com>
     [not found] ` <20161117184950.GP4240@leon.nu>
     [not found]   ` <582E089A.3040106@redhat.com>
     [not found]     ` <20161117200203.GQ4240@leon.nu>
2016-11-17 22:24       ` Or Gerlitz
2016-11-18  2:01         ` Doug Ledford
2016-11-19 19:46           ` Or Gerlitz
2016-11-19 23:11             ` Doug Ledford
2016-11-20 12:53               ` 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=b64700fda3cd5c3cc19d6bf17c948b63a0413645.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).