From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Guy Levi <guyle@mellanox.com>, Ido Kalir <idok@mellanox.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Majd Dibbiny <majd@mellanox.com>,
Mark Zhang <markz@mellanox.com>, Moni Shoua <monis@mellanox.com>
Subject: [PATCH rdma-rc 0/8] Fixes for v5.3
Date: Thu, 15 Aug 2019 11:38:26 +0300 [thread overview]
Message-ID: <20190815083834.9245-1-leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@mellanox.com>
Hi,
This is a collection of new fixes for v5.3, everything here is fixing
kernel crash or visible bug with one exception: patch #5 "IB/mlx5:
Consolidate use_umr checks into single function". That patch is nice
to have improvement to implement rest of the series.
Thanks
Ido Kalir (1):
IB/core: Fix NULL pointer dereference when bind QP to counter
Jason Gunthorpe (1):
RDMA/mlx5: Fix MR npages calculation for IB_ACCESS_HUGETLB
Leon Romanovsky (2):
RDMA/counters: Properly implement PID checks
RDMA/restrack: Rewrite PID namespace check to be reliable
Moni Shoua (4):
IB/mlx5: Consolidate use_umr checks into single function
IB/mlx5: Report and handle ODP support properly
IB/mlx5: Fix MR re-registration flow to use UMR properly
IB/mlx5: Block MR WR if UMR is not possible
drivers/infiniband/core/counters.c | 10 ++++------
drivers/infiniband/core/nldev.c | 3 +--
drivers/infiniband/core/restrack.c | 15 +++++++--------
drivers/infiniband/core/umem.c | 7 +------
drivers/infiniband/hw/mlx5/main.c | 6 +++---
drivers/infiniband/hw/mlx5/mem.c | 5 +++--
drivers/infiniband/hw/mlx5/mlx5_ib.h | 14 ++++++++++++++
drivers/infiniband/hw/mlx5/mr.c | 7 +++----
drivers/infiniband/hw/mlx5/odp.c | 17 +++++++++--------
drivers/infiniband/hw/mlx5/qp.c | 24 +++++++++++++++++++-----
include/rdma/restrack.h | 3 +--
11 files changed, 65 insertions(+), 46 deletions(-)
--
2.20.1
next reply other threads:[~2019-08-15 8:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 8:38 Leon Romanovsky [this message]
2019-08-15 8:38 ` [PATCH rdma-rc 1/8] IB/core: Fix NULL pointer dereference when bind QP to counter Leon Romanovsky
2019-08-15 8:38 ` [PATCH rdma-rc 2/8] RDMA/counters: Properly implement PID checks Leon Romanovsky
2019-08-15 8:38 ` [PATCH rdma-rc 3/8] RDMA/restrack: Rewrite PID namespace check to be reliable Leon Romanovsky
2019-08-15 8:38 ` [PATCH rdma-rc 4/8] RDMA/mlx5: Fix MR npages calculation for IB_ACCESS_HUGETLB Leon Romanovsky
2019-08-15 8:38 ` [PATCH rdma-rc 5/8] IB/mlx5: Consolidate use_umr checks into single function Leon Romanovsky
2019-08-15 8:38 ` [PATCH rdma-rc 6/8] IB/mlx5: Report and handle ODP support properly Leon Romanovsky
2019-08-15 8:38 ` [PATCH rdma-rc 7/8] IB/mlx5: Fix MR re-registration flow to use UMR properly Leon Romanovsky
2019-08-15 8:38 ` [PATCH rdma-rc 8/8] IB/mlx5: Block MR WR if UMR is not possible Leon Romanovsky
2019-08-15 19:29 ` [PATCH rdma-rc 0/8] Fixes for v5.3 Jason Gunthorpe
2019-08-15 20:26 ` Guy Levi(SW)
2019-08-20 16:56 ` Doug Ledford
2019-08-20 17:38 ` Jason Gunthorpe
2019-08-20 17:47 ` Doug Ledford
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=20190815083834.9245-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=guyle@mellanox.com \
--cc=idok@mellanox.com \
--cc=jgg@mellanox.com \
--cc=jgg@ziepe.ca \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=majd@mellanox.com \
--cc=markz@mellanox.com \
--cc=monis@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.