Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965670Ab2JDPm4 (ORCPT ); Thu, 4 Oct 2012 11:42:56 -0400 Received: from e23smtp01.au.ibm.com ([202.81.31.143]:54934 "EHLO e23smtp01.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965644Ab2JDPmx (ORCPT ); Thu, 4 Oct 2012 11:42:53 -0400 Message-ID: <506DAE41.6040007@linux.vnet.ibm.com> Date: Thu, 04 Oct 2012 21:11:53 +0530 From: "Srivatsa S. Bhat" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0 MIME-Version: 1.0 To: Jiri Kosina CC: linux-scsi@vger.kernel.org, James.Bottomley@hansenpartnership.com, "linux-kernel@vger.kernel.org" , Nicholas Bellinger Subject: Re: [qla2xxx] INFO: possible irq lock inversion dependency detected References: <506D80C2.5040405@linux.vnet.ibm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit x-cbid: 12100415-1618-0000-0000-000002970819 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3026 Lines: 89 Hi Jiri, Thanks for taking a look! > This seems to be real. You should be seeing that since 3.5-rc1 already > though ... ? > > Does the patch below fix that? > Yes, it does, thanks! But 3.6-rc kernels were booting fine as far as I remember. I'll check again and get back tomorrow. > > From: Jiri Kosina > Subject: [PATCH] [SCSI] qla2xxx: fix potential deadlock on ha->hardware_lock > > Lockdep reports: > > === [ cut here ] === > ========================================================= > [ INFO: possible irq lock inversion dependency detected ] > 3.6.0-0.0.0.28.36b5ec9-default #1 Not tainted > --------------------------------------------------------- > qla2xxx_1_dpc/368 just changed the state of lock: > (&(&ha->vport_slock)->rlock){+.....}, at: [] qla2x00_configure_hba+0x197/0x3c0 [qla2xxx] > but this lock was taken by another, HARDIRQ-safe lock in the past: > (&(&ha->hardware_lock)->rlock){-.....} > > and interrupts could create inverse lock ordering between them. > > other info that might help us debug this: > Possible interrupt unsafe locking scenario: > > CPU0 CPU1 > ---- ---- > lock(&(&ha->vport_slock)->rlock); > local_irq_disable(); > lock(&(&ha->hardware_lock)->rlock); > lock(&(&ha->vport_slock)->rlock); > > lock(&(&ha->hardware_lock)->rlock); > === [ cut here ] === > > Fix the potential deadlock by disabling IRQs while holding ha->vport_slock. > > Reported-by: Srivatsa S. Bhat > Signed-off-by: Jiri Kosina Tested-by: Srivatsa S. Bhat Regards, Srivatsa S. Bhat > --- > drivers/scsi/qla2xxx/qla_init.c | 5 +++-- > 1 files changed, 3 insertions(+), 2 deletions(-) > > diff --git a/drivers/scsi/qla2xxx/qla_init.c b/drivers/scsi/qla2xxx/qla_init.c > index 799a58b..48fca47 100644 > --- a/drivers/scsi/qla2xxx/qla_init.c > +++ b/drivers/scsi/qla2xxx/qla_init.c > @@ -2080,6 +2080,7 @@ qla2x00_configure_hba(scsi_qla_host_t *vha) > uint8_t domain; > char connect_type[22]; > struct qla_hw_data *ha = vha->hw; > + unsigned long flags; > > /* Get host addresses. */ > rval = qla2x00_get_adapter_id(vha, > @@ -2154,9 +2155,9 @@ qla2x00_configure_hba(scsi_qla_host_t *vha) > vha->d_id.b.area = area; > vha->d_id.b.al_pa = al_pa; > > - spin_lock(&ha->vport_slock); > + spin_lock_irqsave(&ha->vport_slock, flags); > qlt_update_vp_map(vha, SET_AL_PA); > - spin_unlock(&ha->vport_slock); > + spin_unlock_irqrestore(&ha->vport_slock, flags); > > if (!vha->flags.init_done) > ql_log(ql_log_info, vha, 0x2010, > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/