Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, frank.zago@hpe.com, ian.ziemba@hpe.com,
	jhack@hpe.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next v16 0/2] Fix race conditions in rxe_pool
Date: Thu, 30 Jun 2022 10:58:17 -0300	[thread overview]
Message-ID: <20220630135817.GA982692@nvidia.com> (raw)
In-Reply-To: <20220612223434.31462-1-rpearsonhpe@gmail.com>

On Sun, Jun 12, 2022 at 05:34:33PM -0500, 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 includes the remaining two
> patches of the original series.
> 
> Applies cleanly to current for-next after the two oneline patches
> submitted by Dongliang Mu that fixed an error in the error checking
> code from xa_alloc_cyclic().

Applied to for-next, thanks

I moved the might_sleep hunk from the last patch to the first though

Jason

  parent reply	other threads:[~2022-06-30 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12 22:34 [PATCH for-next v16 0/2] Fix race conditions in rxe_pool Bob Pearson
2022-06-12 22:34 ` [PATCH v16 1/2] RDMA/rxe: Stop lookup of partially built objects Bob Pearson
2022-06-12 22:34 ` [PATCH v16 2/2] RDMA/rxe: Convert read side locking to rcu Bob Pearson
2022-06-30 13:58 ` Jason Gunthorpe [this message]
2022-06-30 16:58   ` [PATCH for-next v16 0/2] Fix race conditions in rxe_pool 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=20220630135817.GA982692@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=frank.zago@hpe.com \
    --cc=ian.ziemba@hpe.com \
    --cc=jhack@hpe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox