From: Bob Pearson <rpearsonhpe@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>
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 16:06:23 -0500 [thread overview]
Message-ID: <ca8722e6-db2d-0ab1-b8af-0932017df23e@gmail.com> (raw)
In-Reply-To: <d80141c8-04ee-e6ed-34d8-5cf43b49fd55@acm.org>
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.
>
> Hi Bob,
>
> 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.
>
> Thanks,
>
> Bart.
From your note I can't figure out what you are running. Can you give me more details about the failing test case?
Bob
next prev parent reply other threads:[~2022-04-07 21:06 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 [this message]
2022-04-07 21:44 ` Bart Van Assche
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=ca8722e6-db2d-0ab1-b8af-0932017df23e@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=bvanassche@acm.org \
--cc=linux-rdma@vger.kernel.org \
--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 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.