public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Bernard Metzler <BMT@zurich.ibm.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	Daniel Wagner <wagi@kernel.org>
Subject: Re: [bug report] blktests nvme/061 hang with rdma transport and siw driver
Date: Thu, 8 May 2025 09:25:39 -0300	[thread overview]
Message-ID: <20250508122539.GA6371@ziepe.ca> (raw)
In-Reply-To: <d4xfwos54mccrwgw76t6q5nhwe2n3bxbt46cmyuhjcpcsub2hy@7d3zsewjkycv>

On Thu, May 08, 2025 at 07:03:03AM +0000, Shinichiro Kawasaki wrote:
> One left question is why the failure was not observed with rxe driver, but with
> siw driver. My mere guess is that is because siw driver calls id->add_ref() and
> cm_id->rem_ref().

Only siw uses the code in iwcm.c, rxe does not.

Bernard? What do you think about this analysis? I've never really
looked inside iwcm.c..

Thanks,
Jason

  reply	other threads:[~2025-05-08 12:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 11:13 [bug report] blktests nvme/061 hang with rdma transport and siw driver Shinichiro Kawasaki
2025-04-15 13:09 ` Bernard Metzler
2025-04-15 15:00   ` Zhu Yanjun
2025-04-16  2:50     ` Shinichiro Kawasaki
2025-04-16  5:14       ` Zhu Yanjun
2025-04-15 15:18 ` Bernard Metzler
2025-04-16  3:42   ` Shinichiro Kawasaki
2025-05-08  7:03     ` Shinichiro Kawasaki
2025-05-08 12:25       ` Jason Gunthorpe [this message]
2025-05-08 14:23         ` Bernard Metzler
2025-05-09  9:03           ` Shinichiro Kawasaki
2025-05-08 14:22       ` Bernard Metzler
2025-05-09 10:21       ` Zhu Yanjun
2025-05-10  9:59         ` Shinichiro Kawasaki
2025-05-10 10:04       ` Shinichiro Kawasaki

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=20250508122539.GA6371@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=BMT@zurich.ibm.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=wagi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox