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 17:06:59 -0700 [thread overview]
Message-ID: <fd17d243-f98f-517e-0344-60fe4e326728@acm.org> (raw)
In-Reply-To: <92181dc8-dadc-3df6-3ecc-e2dca9047be4@gmail.com>
On 4/7/22 15:34, Bob Pearson wrote:
> It looks like on 5.18-rc1+ blktest is not running for me. (Last time I ran it was pre 5.18)
> I am not seeing the Warning but instead it just hangs? Are you enabling some lock checking
> that I am not? If so how?
Hi Bob,
The warning shown in the email at the start of this thread has been
reported by lockdep. I think that you will need to enable at least the
following in the kernel configuration:
CONFIG_LOCKDEP=y
CONFIG_PROVE_LOCKING=y
Thanks,
Bart.
next prev parent reply other threads:[~2022-04-08 0:07 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
2022-04-07 21:46 ` Bob Pearson
2022-04-07 22:34 ` Bob Pearson
2022-04-08 0:06 ` Bart Van Assche [this message]
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=fd17d243-f98f-517e-0344-60fe4e326728@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