From: Jason Gunthorpe <jgg@ziepe.ca>
To: linux-rdma@vger.kernel.org
Subject: Re: [PATCH -rc 0/6] Bug fixes for odp
Date: Fri, 4 Oct 2019 15:55:32 -0300 [thread overview]
Message-ID: <20191004185532.GA20755@ziepe.ca> (raw)
In-Reply-To: <20191001153821.23621-1-jgg@ziepe.ca>
On Tue, Oct 01, 2019 at 12:38:15PM -0300, Jason Gunthorpe wrote:
> From: Jason Gunthorpe <jgg@mellanox.com>
>
> Various assorted bug fixes for the ODP feature closing races and other bad
> locking things we be seeing in the field.
>
> Jason Gunthorpe (6):
> RDMA/mlx5: Do not allow rereg of a ODP MR
> RDMA/mlx5: Fix a race with mlx5_ib_update_xlt on an implicit MR
> RDMA/odp: Lift umem_mutex out of ib_umem_odp_unmap_dma_pages()
> RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu
> RDMA/mlx5: Put live in the correct place for ODP MRs
> RDMA/mlx5: Add missing synchronize_srcu() for MW cases
Applied to for-rc
Jason
prev parent reply other threads:[~2019-10-04 18:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 15:38 [PATCH -rc 0/6] Bug fixes for odp Jason Gunthorpe
2019-10-01 15:38 ` [PATCH 1/6] RDMA/mlx5: Do not allow rereg of a ODP MR Jason Gunthorpe
2019-10-01 15:38 ` [PATCH 2/6] RDMA/mlx5: Fix a race with mlx5_ib_update_xlt on an implicit MR Jason Gunthorpe
2019-10-02 8:18 ` Leon Romanovsky
2019-10-02 14:39 ` Jason Gunthorpe
2019-10-02 15:41 ` Leon Romanovsky
2019-10-03 12:48 ` Jason Gunthorpe
2019-10-01 15:38 ` [PATCH 3/6] RDMA/odp: Lift umem_mutex out of ib_umem_odp_unmap_dma_pages() Jason Gunthorpe
2019-10-01 15:38 ` [PATCH 4/6] RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu Jason Gunthorpe
2019-10-01 15:38 ` [PATCH 5/6] RDMA/mlx5: Put live in the correct place for ODP MRs Jason Gunthorpe
2019-10-01 15:38 ` [PATCH 6/6] RDMA/mlx5: Add missing synchronize_srcu() for MW cases Jason Gunthorpe
2019-10-03 8:54 ` Leon Romanovsky
2019-10-03 12:33 ` Jason Gunthorpe
2019-10-04 18:55 ` Jason Gunthorpe [this message]
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=20191004185532.GA20755@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=linux-rdma@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).