From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>, <linux-rdma@vger.kernel.org>,
Yishai Hadas <yishaih@nvidia.com>
Subject: Re: [PATCH rdma-next 0/5] Clean up rereg_mr handling
Date: Mon, 7 Dec 2020 15:33:50 -0400 [thread overview]
Message-ID: <20201207193350.GA1762196@nvidia.com> (raw)
In-Reply-To: <20201130075839.278575-1-leon@kernel.org>
On Mon, Nov 30, 2020 at 09:58:34AM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> The mlx5 rereg_mr implementation is convoluted. Such code causes
> to hard to spot bugs and even harder task - code review.
>
> This series from Jason cleans that flow.
>
> Thanks
>
> Jason Gunthorpe (5):
> RDMA/uverbs: Tidy input validation of ib_uverbs_rereg_mr()
> RDMA/uverbs: Check ODP in ib_check_mr_access() as well
> RDMA/uverbs: Allow drivers to create a new HW object during rereg_mr
> RDMA/mlx5: Reorganize mlx5_ib_reg_user_mr()
> RDMA/mlx5: Fix error unwinds for rereg_mr
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2020-12-07 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 7:58 [PATCH rdma-next 0/5] Clean up rereg_mr handling Leon Romanovsky
2020-11-30 7:58 ` [PATCH rdma-next 1/5] RDMA/uverbs: Tidy input validation of ib_uverbs_rereg_mr() Leon Romanovsky
2020-11-30 7:58 ` [PATCH rdma-next 2/5] RDMA/uverbs: Check ODP in ib_check_mr_access() as well Leon Romanovsky
2020-11-30 7:58 ` [PATCH rdma-next 3/5] RDMA/uverbs: Allow drivers to create a new HW object during rereg_mr Leon Romanovsky
2020-11-30 7:58 ` [PATCH rdma-next 4/5] RDMA/mlx5: Reorganize mlx5_ib_reg_user_mr() Leon Romanovsky
2020-11-30 7:58 ` [PATCH rdma-next 5/5] RDMA/mlx5: Fix error unwinds for rereg_mr Leon Romanovsky
2020-12-07 19:33 ` 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=20201207193350.GA1762196@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=yishaih@nvidia.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.