Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: RDMA mailing list <linux-rdma@vger.kernel.org>,
	Yi Zhang <yi.zhang@redhat.com>
Subject: Re: [bug report] rdma_rxe: WARNING: inconsistent lock state, inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage
Date: Thu, 7 Apr 2022 14:44:09 -0700	[thread overview]
Message-ID: <f7b84702-8001-70bf-2f26-704548b96279@acm.org> (raw)
In-Reply-To: <ca8722e6-db2d-0ab1-b8af-0932017df23e@gmail.com>

On 4/7/22 14:06, Bob Pearson wrote:
> On 4/7/22 14:49, Bart Van Assche wrote:
>> On 4/7/22 12:15, Robert Pearson wrote:
>>> I would say it is very possible. There was a period when the
>>> pool locks were switched to _bh spinlocks but that was later
>>> reversed back to _irqsave locks which cleaned up some failures. I
>>> don't know which version Yi Zhang was using. The root cause of
>>> this bug was caused by librdmacm making verbs API calls while
>>> holding _irqsave locks which I didn't figure out until later.
>> 
>> I can reproduce the issue Yi reported with kernel v5.18-rc1. Please
>> let me know if you need any additional information to reproduce
>> this issue.
> 
> From your note I can't figure out what you are running. Can you give
> me more details about the failing test case?

Hi Bob,

In Yi's email I found the following:

run blktests srp/001

That test case can be run as follows:

git clone https://github.com/osandov/blktests && cd blktests && make && 
sudo ./check -q srp/001

Thanks,

Bart.


  reply	other threads:[~2022-04-07 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  3:08 [bug report] rdma_rxe: WARNING: inconsistent lock state, inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage Yi Zhang
2022-04-07 18:51 ` Bart Van Assche
2022-04-07 19:15   ` Robert Pearson
2022-04-07 19:49     ` Bart Van Assche
2022-04-07 21:06       ` Bob Pearson
2022-04-07 21:44         ` Bart Van Assche [this message]
2022-04-07 21:46           ` Bob Pearson
2022-04-07 22:34           ` Bob Pearson
2022-04-08  0:06             ` Bart Van Assche
2022-04-08  5:07 ` Yanjun Zhu
2022-04-08  9:10   ` Yi Zhang
2022-04-09  3:27     ` Yanjun Zhu
2022-04-09  5:33       ` Yi Zhang
2022-04-09 12:13         ` Yanjun Zhu
2022-04-09 14:00           ` Yanjun Zhu
2022-04-09 23:57             ` Yanjun Zhu
2022-04-10 13:12               ` 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=f7b84702-8001-70bf-2f26-704548b96279@acm.org \
    --to=bvanassche@acm.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.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