On 2/10/2019 4:04 PM, Bart Van Assche wrote:
Hi James,
Has the lpfc driver been tested recently with lockdep enabled? This is
what appeared in the kernel log on my test setup when I tried to use the
lpfc driver:
WARNING: CPU: 0 PID: 22263 at drivers/scsi/lpfc/lpfc_sli.c:9882
__lpfc_sli_issue_iocb_s4+0x34e/0x380 [lpfc]
CPU: 0 PID: 22263 Comm: lpfc_worker_1 Tainted: G O 5.0.0-rc6-dbg+ #2
Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
RIP: 0010:__lpfc_sli_issue_iocb_s4+0x34e/0x380 [lpfc]
Call Trace:
lpfc_sli_issue_iocb+0xcb/0x220 [lpfc]
lpfc_issue_fabric_iocb+0x1fe/0x270 [lpfc]
lpfc_issue_els_flogi+0x352/0x620 [lpfc]
lpfc_initial_flogi+0x61/0xd0 [lpfc]
lpfc_mbx_cmpl_local_config_link+0x112/0x2e0 [lpfc]
lpfc_sli_handle_mb_event+0x455/0x8b0 [lpfc]
lpfc_do_work+0x15a7/0x2630 [lpfc]
kthread+0x1d2/0x1f0
ret_from_fork+0x3a/0x50
This is what I found on line 9882:
lockdep_assert_held(&phba->hbalock);
Thanks,
Bart.
I expect this recent popped up with the 12.2.0.0 patches. I'll look at it.
-- james
