linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	Daniel Wagner <dwagner@suse.de>,
	Leon Romanovsky <leon@kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH v2] RDMA/cma: prevent rdma id destroy during cma_iw_handler
Date: Thu, 7 Sep 2023 13:17:02 -0300	[thread overview]
Message-ID: <ZPn3fryQDQeckq4k@ziepe.ca> (raw)
In-Reply-To: <CAHj4cs_mP7kmnKdm--tEkb_yE0saA7A_BBV21E1RQT8a+J7s0g@mail.gmail.com>

On Thu, Sep 07, 2023 at 03:47:03PM +0800, Yi Zhang wrote:
> Seems I reproduced this issue[3] when I run [1] on the latest
> linux-block/for-next with kernel config[2].

https://lore.kernel.org/linux-rdma/13441b9b-cc13-f0e0-bd46-f14983dadd49@grimberg.me/

So far nobody has come with a solution

Jason

  reply	other threads:[~2023-09-07 16:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  5:42 [PATCH v2] RDMA/cma: prevent rdma id destroy during cma_iw_handler Shin'ichiro Kawasaki
2023-06-12  7:13 ` Leon Romanovsky
2023-06-12 14:18 ` Jason Gunthorpe
2023-06-13  1:43   ` Shinichiro Kawasaki
2023-06-13  6:47     ` Shinichiro Kawasaki
2023-06-13 13:30     ` Jason Gunthorpe
2023-06-13 18:07       ` Leon Romanovsky
2023-06-14  7:53         ` Shinichiro Kawasaki
2023-06-14 17:36           ` Jason Gunthorpe
2023-06-15  0:45             ` Shinichiro Kawasaki
2023-09-05  0:39               ` Shinichiro Kawasaki
2023-09-06  8:54                 ` Daniel Wagner
2023-09-06 11:31                   ` Shinichiro Kawasaki
2023-09-07  7:47                     ` Yi Zhang
2023-09-07 16:17                       ` Jason Gunthorpe [this message]
2023-09-08  7:18                       ` Hannes Reinecke
2023-09-08  8:33                         ` Yi Zhang

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=ZPn3fryQDQeckq4k@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=dlemoal@kernel.org \
    --cc=dwagner@suse.de \
    --cc=leon@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=yi.zhang@redhat.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;
as well as URLs for NNTP newsgroup(s).