mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Smart <jsmart2021@gmail.com>
To: Jia-Ju Bai <baijiaju1990@gmail.com>,
	james.smart@broadcom.com, dick.kennedy@broadcom.com,
	jejb@linux.ibm.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] scsi: lpfc: possible ABBA deadlock
Date: Sat, 24 Jul 2021 13:18:27 -0700	[thread overview]
Message-ID: <5496b03b-49aa-88e3-e058-1d97c91b1b0b@gmail.com> (raw)
In-Reply-To: <652256c8-6fce-a506-76a9-e1502a5ff82e@gmail.com>

On 7/15/2021 3:37 AM, Jia-Ju Bai wrote:
> Hello,
> 
> I find there is a possible ABBA deadlock in the lpfc driver in Linux 5.10:
> 
> In lpfc_nvmet_unsol_fcp_issue_abort():
> 3502:     spin_lock_irqsave(&ctxp->ctxlock, flags);
> 3504: spin_lock(&phba->sli4_hba.abts_nvmet_buf_list_lock);
> 
> In lpfc_sli4_nvmet_xri_aborted():
> 1787: spin_lock(&phba->sli4_hba.abts_nvmet_buf_list_lock);
> 1794:     spin_lock(&ctxp->ctxlock);
> 
> When lpfc_nvmet_unsol_fcp_issue_abort() and 
> lpfc_sli4_nvmet_xri_aborted() are concurrently executed, the deadlock 
> can occur.
> 
> I am not quite sure whether this possible deadlock is real and how to 
> fix it if it is real.
> Any feedback would be appreciated, thanks :)
> 
> 
> Best wishes,
> Jia-Ju Bai

Jia-Ju,

It's a valid issue, but rather difficult to actually occur. We've put 
together a fix and am testing it. Will post when ready.

-- james


      reply	other threads:[~2021-07-24 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 10:37 Jia-Ju Bai
2021-07-24 20:18 ` James Smart [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=5496b03b-49aa-88e3-e058-1d97c91b1b0b@gmail.com \
    --to=jsmart2021@gmail.com \
    --cc=baijiaju1990@gmail.com \
    --cc=dick.kennedy@broadcom.com \
    --cc=james.smart@broadcom.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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

Powered by JetHome