All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Leon Romanovsky <leon@kernel.org>, Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
	RDMA mailing list <linux-rdma@vger.kernel.org>,
	Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH rdma-rc 0/2] RDMA fixes for 5.3
Date: Wed, 31 Jul 2019 11:29:25 -0400	[thread overview]
Message-ID: <22c618d7d496787c0d682d618249de21d1dcf082.camel@redhat.com> (raw)
In-Reply-To: <20190731081841.32345-1-leon@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 704 bytes --]

On Wed, 2019-07-31 at 11:18 +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
> 
> Hi,
> 
> Two lock fixes in device<->client interaction, please see
> extensive commit messages for more details.
> 
> Thanks
> 
> Jason Gunthorpe (2):
>   RDMA/devices: Do not deadlock during client removal
>   RDMA/devices: Remove the lock around remove_client_context

I tried to figure out some way to trip either of these up, but they both
look good to me.  I'll let them sit on the list for feedback before I
take them though.

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2019-07-31 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31  8:18 [PATCH rdma-rc 0/2] RDMA fixes for 5.3 Leon Romanovsky
2019-07-31  8:18 ` [PATCH rdma-rc 1/2] RDMA/devices: Do not deadlock during client removal Leon Romanovsky
2019-07-31  8:18 ` [PATCH rdma-rc 2/2] RDMA/devices: Remove the lock around remove_client_context Leon Romanovsky
2019-07-31 15:29 ` Doug Ledford [this message]
2019-08-01 15:47   ` [PATCH rdma-rc 0/2] RDMA fixes for 5.3 Doug Ledford

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=22c618d7d496787c0d682d618249de21d1dcf082.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=leonro@mellanox.com \
    --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 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.