All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Bart Van Assche <bvanassche@acm.org>,
	Bob Pearson <rpearsonhpe@gmail.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: Inconsistent lock state warning for rxe_poll_cq()
Date: Tue, 15 Feb 2022 12:50:39 +0800	[thread overview]
Message-ID: <6d4360db-af4d-3c85-c035-2d08c0e28685@linux.dev> (raw)
In-Reply-To: <8f9fe1da-c302-0c45-8df8-2905c630daad@acm.org>



On 2/15/22 2:01 AM, Bart Van Assche wrote:
> Hi Bob,
>
> If I run the SRP tests against Jason's rdma/for-next branch then these
> tests pass if I use the siw driver but not if I use the rdma_rxe driver.
> Can you please take a look at the output triggered by running blktests?
> If I run blktests as follows: ./check -q srp, the following output
> appears:
>
> WARNING: CPU: 1 PID: 1052 at kernel/softirq.c:363 
> __local_bh_enable_ip+0xa4/0xf0
>  _raw_write_unlock_bh+0x31/0x40
>  __rxe_add_index+0x38/0x50 [rdma_rxe]
>  rxe_create_ah+0xce/0x1b0 [rdma_rxe]
>  _rdma_create_ah+0x2c8/0x2f0 [ib_core]
>  rdma_create_ah+0xfd/0x1c0 [ib_core]
>  cm_alloc_msg+0xbc/0x280 [ib_cm]
>  cm_alloc_priv_msg+0x2d/0x70 [ib_cm]
>  ib_send_cm_req+0x4fe/0x830 [ib_cm]
>  cma_connect_ib+0x3c4/0x600 [rdma_cm]
>  rdma_connect_locked+0x145/0x490 [rdma_cm]
>  rdma_connect+0x31/0x50 [rdma_cm]
>  srp_send_req+0x58a/0x830 [ib_srp]
>  srp_connect_ch+0x9f/0x1d0 [ib_srp]
>  add_target_store+0xa6b/0xf20 [ib_srp]
>  dev_attr_store+0x3e/0x60
>  sysfs_kf_write+0x87/0xa0
>  kernfs_fop_write_iter+0x1c7/0x270
>  new_sync_write+0x296/0x3c0
>  vfs_write+0x43c/0x580
>  ksys_write+0xd9/0x180
>  __x64_sys_write+0x42/0x50
>  do_syscall_64+0x35/0x80
>  entry_SYSCALL_64_after_hwframe+0x44/0xae

I think it is exactly the same which I encountered with 5.17-rc3.

https://lore.kernel.org/linux-rdma/20220210073655.42281-1-guoqing.jiang@linux.dev/T/#m0c0ce0745078095ea931f61d2b1c6ce0fdd5403b

Thanks,
Guoqing

      parent reply	other threads:[~2022-02-15  4:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 18:01 Inconsistent lock state warning for rxe_poll_cq() Bart Van Assche
2022-02-14 19:51 ` Bob Pearson
2022-02-14 19:55   ` Bart Van Assche
2022-02-14 20:25     ` Bob Pearson
2022-02-14 20:48       ` Bart Van Assche
2022-02-15  5:43         ` Bob Pearson
2022-02-15 12:16           ` Guoqing Jiang
2022-02-15 14:41           ` Jason Gunthorpe
2022-02-15 16:45             ` Pearson, Robert B
2022-02-15 16:48               ` Jason Gunthorpe
2022-02-15 16:53                 ` Pearson, Robert B
2022-02-15 17:01                   ` Jason Gunthorpe
2022-02-15 17:18                     ` Haakon Bugge
2022-02-15  4:50 ` Guoqing Jiang [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:
  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=6d4360db-af4d-3c85-c035-2d08c0e28685@linux.dev \
    --to=guoqing.jiang@linux.dev \
    --cc=bvanassche@acm.org \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.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.