All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: jgg@nvidia.com, zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next 0/6] RDMA/rxe: Fix potential races
Date: Tue, 12 Oct 2021 09:34:56 +0300	[thread overview]
Message-ID: <YWUskJBU5ZHrIhhS@unreal> (raw)
In-Reply-To: <20211010235931.24042-1-rpearsonhpe@gmail.com>

On Sun, Oct 10, 2021 at 06:59:25PM -0500, Bob Pearson wrote:
> There are possible race conditions related to attempting to access
> rxe pool objects at the same time as the pools or elements are being
> freed. This series of patches addresses these races.

Can we get rid of this pool?

Thanks

> 
> Bob Pearson (6):
>   RDMA/rxe: Make rxe_alloc() take pool lock
>   RDMA/rxe: Copy setup parameters into rxe_pool
>   RDMA/rxe: Save object pointer in pool element
>   RDMA/rxe: Combine rxe_add_index with rxe_alloc
>   RDMA/rxe: Combine rxe_add_key with rxe_alloc
>   RDMA/rxe: Fix potential race condition in rxe_pool
> 
>  drivers/infiniband/sw/rxe/rxe_mcast.c |   5 +-
>  drivers/infiniband/sw/rxe/rxe_mr.c    |   1 -
>  drivers/infiniband/sw/rxe/rxe_mw.c    |   5 +-
>  drivers/infiniband/sw/rxe/rxe_pool.c  | 235 +++++++++++++-------------
>  drivers/infiniband/sw/rxe/rxe_pool.h  |  67 +++-----
>  drivers/infiniband/sw/rxe/rxe_verbs.c |  10 --
>  6 files changed, 140 insertions(+), 183 deletions(-)
> 
> -- 
> 2.30.2
> 

  parent reply	other threads:[~2021-10-12  6:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10 23:59 [PATCH for-next 0/6] RDMA/rxe: Fix potential races Bob Pearson
2021-10-10 23:59 ` [PATCH for-next 1/6] RDMA/rxe: Make rxe_alloc() take pool lock Bob Pearson
2021-10-20 23:16   ` Jason Gunthorpe
2021-10-21 17:46     ` Bob Pearson
2021-10-25 12:43       ` Jason Gunthorpe
2021-10-25 18:48         ` Robert Pearson
2021-10-10 23:59 ` [PATCH for-next 2/6] RDMA/rxe: Copy setup parameters into rxe_pool Bob Pearson
2021-10-10 23:59 ` [PATCH for-next 3/6] RDMA/rxe: Save object pointer in pool element Bob Pearson
2021-10-20 23:20   ` Jason Gunthorpe
2021-10-21 17:21     ` Bob Pearson
2021-10-25 15:40       ` Jason Gunthorpe
2021-10-10 23:59 ` [PATCH for-next 4/6] RDMA/rxe: Combine rxe_add_index with rxe_alloc Bob Pearson
2021-10-10 23:59 ` [PATCH for-next 5/6] RDMA/rxe: Combine rxe_add_key " Bob Pearson
2021-10-10 23:59 ` [PATCH for-next 6/6] RDMA/rxe: Fix potential race condition in rxe_pool Bob Pearson
2021-10-20 23:23   ` Jason Gunthorpe
2021-10-12  6:34 ` Leon Romanovsky [this message]
2021-10-12 20:19   ` [PATCH for-next 0/6] RDMA/rxe: Fix potential races Bob Pearson
2021-10-19 13:07     ` Leon Romanovsky
2021-10-19 16:35       ` Bob Pearson
2021-10-19 18:43         ` Jason Gunthorpe
2021-10-19 22:51           ` Bob Pearson

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=YWUskJBU5ZHrIhhS@unreal \
    --to=leon@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.com \
    --cc=zyjzyj2000@gmail.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.