Linux-RDMA Archive on
 help / color / Atom feed
From: Jason Gunthorpe <>
To: Bart Van Assche <>
Cc: "" <>
Subject: Re: rdma-for-next lockdep complaint
Date: Fri, 22 May 2020 22:11:02 -0300
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, May 22, 2020 at 02:29:15PM -0700, Bart Van Assche wrote:
> Hi,
> If I run test srp/015 from the blktests test suite then the lockdep complaint
> shown below is reported. Since I haven't seen this complaint in the past I
> think that this is a regression. This complaint was triggered by the code on
> the for-next branch of
> git:// Is this a known
> issue?

I haven't seen it before, and it doesn't look like anything changed
here lately.

I think your test must have got unlucky to hit one of the
rdma_destroy_id paths.

It looks like a false positive from lockdep as these are never the
same lock.

Perhaps it could be fixed by lifting the mutex_unlock to before
the rdma_destroy_id ? Would need some study


      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 21:29 Bart Van Assche
2020-05-23  1:11 ` Jason Gunthorpe [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-RDMA Archive on

Archives are clonable:
	git clone --mirror linux-rdma/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-rdma linux-rdma/ \
	public-inbox-index linux-rdma

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone