From: Bob Pearson <rpearsonhpe@gmail.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next v11 00/13] Fix race conditions in rxe_pool
Date: Tue, 15 Mar 2022 23:05:48 -0500 [thread overview]
Message-ID: <883b72de-850c-7b4d-fdaf-457f23d309ea@gmail.com> (raw)
In-Reply-To: <20220316002515.GZ11336@nvidia.com>
On 3/15/22 19:25, Jason Gunthorpe wrote:
> On Thu, Mar 03, 2022 at 06:07:56PM -0600, Bob Pearson wrote:
>> There are several race conditions discovered in the current rdma_rxe
>> driver. They mostly relate to races between normal operations and
>> destroying objects. This patch series
>> - Makes several minor cleanups in rxe_pool.[ch]
>> - Replaces the red-black trees currently used by xarrays for indices
>> - Corrects several reference counting errors
>> - Adds wait for completions to the paths in verbs APIs which destroy
>> objects.
>> - Changes read side locking to rcu.
>>
>> Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
>> v11
>> Rebased to current for-next.
>> Reordered patches and made other changes to respond to issues
>> reported by Jason Gunthorpe.
>> v10
>> Rebased to current wip/jgg-for-next.
>> Split some patches into smaller ones.
>> v9
>> Corrected issues reported by Jason Gunthorpe,
>> Converted locking in rxe_mcast.c and rxe_pool.c to use RCU
>> Split up the patches into smaller changes
>> v8
>> Fixed an additional race in 3/8 which was not handled correctly.
>> v7
>> Corrected issues reported by Jason Gunthorpe
>> Link: https://lore.kernel.org/linux-rdma/20211207190947.GH6385@nvidia.com/
>> Link: https://lore.kernel.org/linux-rdma/20211207191857.GI6385@nvidia.com/
>> Link: https://lore.kernel.org/linux-rdma/20211207192824.GJ6385@nvidia.com/
>> v6
>> Fixed a kzalloc flags bug.
>> Fixed comment bug reported by 'Kernel Test Robot'.
>> Changed type of rxe_pool.c in __rxe_fini().
>> v5
>> Removed patches already accepted into for-next and addressed comments
>> from Jason Gunthorpe.
>> v4
>> Restructured patch series to change to xarray earlier which
>> greatly simplified the changes.
>> Rebased to current for-next
>> v3
>> Changed rxe_alloc to use GFP_KERNEL
>> Addressed other comments by Jason Gunthorp
>> Merged the previous 06/10 and 07/10 patches into one since they overlapped
>> Added some minor cleanups as 10/10
>> v2
>> Rebased to current for-next.
>> Added 4 additional patches
>>
>> Bob Pearson (13):
>> RDMA/rxe: Fix ref error in rxe_av.c
>> RDMA/rxe: Replace mr by rkey in responder resources
>> RDMA/rxe: Reverse the sense of RXE_POOL_NO_ALLOC
>> RDMA/rxe: Delete _locked() APIs for pool objects
>> RDMA/rxe: Replace obj by elem in declaration
>> RDMA/rxe: Move max_elem into rxe_type_info
>> RDMA/rxe: Shorten pool names in rxe_pool.c
>> RDMA/rxe: Replace red-black trees by xarrays
>> RDMA/rxe: Use standard names for ref counting
>
> If you let me know about the WARN_ON I think up to here is good
>
> Thanks,
> Jason
I agreed to the change.
next prev parent reply other threads:[~2022-03-16 4:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 0:07 [PATCH for-next v11 00/13] Fix race conditions in rxe_pool Bob Pearson
2022-03-04 0:07 ` [PATCH for-next v11 01/13] RDMA/rxe: Fix ref error in rxe_av.c Bob Pearson
2022-03-04 0:07 ` [PATCH for-next v11 02/13] RDMA/rxe: Replace mr by rkey in responder resources Bob Pearson
2022-03-04 0:07 ` [PATCH for-next v11 03/13] RDMA/rxe: Reverse the sense of RXE_POOL_NO_ALLOC Bob Pearson
2022-03-04 0:08 ` [PATCH for-next v11 04/13] RDMA/rxe: Delete _locked() APIs for pool objects Bob Pearson
2022-03-04 0:08 ` [PATCH for-next v11 05/13] RDMA/rxe: Replace obj by elem in declaration Bob Pearson
2022-03-04 0:08 ` [PATCH for-next v11 06/13] RDMA/rxe: Move max_elem into rxe_type_info Bob Pearson
2022-03-04 0:08 ` [PATCH for-next v11 07/13] RDMA/rxe: Shorten pool names in rxe_pool.c Bob Pearson
2022-03-04 0:08 ` [PATCH for-next v11 08/13] RDMA/rxe: Replace red-black trees by xarrays Bob Pearson
2022-03-15 23:45 ` Jason Gunthorpe
2022-03-16 3:05 ` Bob Pearson
2022-03-04 0:08 ` [PATCH for-next v11 09/13] RDMA/rxe: Use standard names for ref counting Bob Pearson
2022-03-04 0:08 ` [PATCH for-next v11 10/13] RDMA/rxe: Stop lookup of partially built objects Bob Pearson
2022-03-16 0:16 ` Jason Gunthorpe
2022-03-16 3:55 ` Bob Pearson
2022-03-16 13:42 ` Jason Gunthorpe
2022-03-04 0:08 ` [PATCH for-next v11 11/13] RDMA/rxe: Add wait_for_completion to pool objects Bob Pearson
2022-03-16 0:17 ` Jason Gunthorpe
2022-03-16 3:57 ` Bob Pearson
2022-03-16 13:43 ` Jason Gunthorpe
2022-03-04 0:08 ` [PATCH for-next v11 12/13] RDMA/rxe: Convert read side locking to rcu Bob Pearson
2022-03-16 0:18 ` Jason Gunthorpe
2022-03-16 4:05 ` Bob Pearson
2022-03-04 0:08 ` [PATCH for-next v11 13/13] RDMA/rxe: Cleanup rxe_pool.c Bob Pearson
2022-03-16 0:25 ` [PATCH for-next v11 00/13] Fix race conditions in rxe_pool Jason Gunthorpe
2022-03-16 4:05 ` Bob Pearson [this message]
2022-03-16 16:08 ` Jason Gunthorpe
2022-03-16 16:09 ` Pearson, Robert B
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=883b72de-850c-7b4d-fdaf-457f23d309ea@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox