Received: by 2002:a05:6a10:6006:0:0:0:0 with SMTP id w6csp308765pxa; Thu, 27 Aug 2020 02:59:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzYFFMmeCLwreHF9DkBYkZ1jvowfeLGSsa+BgroSLVUlwknIq0749vGrXs6UxTHnx0mc6SD X-Received: by 2002:a50:dac6:: with SMTP id s6mr19027384edj.378.1598522380922; Thu, 27 Aug 2020 02:59:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598522380; cv=none; d=google.com; s=arc-20160816; b=q4TX4L5X9ATGXO8nRefY9MV+qpCYnDqp2jkOrngfFBzIBGNsX3f/q5UC0Q3H1Jx/SE xfAGQZgAZGh2uiuP6xfGjzs0LMAPVATUsidZ4KOOubFX9Y3Dz7XjAYuXiHWKSxZT70Zo b58Ubi0EK5Be8Y6ETVkxhWfKqn09/9dVUOgnE3i43nHwjIkl1NfC9vLYqGcepIQTo81a GxVzgIAdBaL6PU/4Hc5X1fF2oKf9Q/Vh+BNgC+k7M1rleKJnU03xsaBhTbC5pFQ9h4nD +54KSV3hzK7EzHf89OxFJ4jP0SiSDqr8GRoX0Q1dxe6X20TS3jNL0mnyVzVjlbHqeoq3 zA3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=zfJqgQyfxcQxZGFUsSZSRiXFeKkjup1Mt1mVfDKhHd0=; b=AaXO3kK4HR2poe/y/FC1BSwdnM9HeL9HzYr7yhZcogUB0rBD4PCZLTlDUrz4YUXYaL PoYDzGIZrWlIU4O7WT3rE4qiN8izxsJjp6hsRqwFIFqp8xeyAT9mMyuPFmmx6S+C1KW7 ngTSRvCWKSIMjtaIpn8k+V6FWWIzwwET6HWBXn7bUzaWLPvOfwqF3WZfULM0El0bp2Dr dXoxxMlMEsYVV9+v4JinU+1XzAWaJ/556PiOnbcQ1gQJgjlJngQTBJOoQdysE9GKELdD mq4ekNyaAf2wvNnEwrvl8wkwR0Bj+YQN667vMM8hdlmNX1+0bXbEXnfpgPjHJL7ZZu1k QeEw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u22si985114eja.418.2020.08.27.02.59.18; Thu, 27 Aug 2020 02:59:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728544AbgH0J6h (ORCPT + 99 others); Thu, 27 Aug 2020 05:58:37 -0400 Received: from mx2.suse.de ([195.135.220.15]:37236 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728463AbgH0J6d (ORCPT ); Thu, 27 Aug 2020 05:58:33 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 24018AE39; Thu, 27 Aug 2020 09:59:03 +0000 (UTC) From: Daniel Wagner To: linux-scsi@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Nilesh Javali , Daniel Wagner Subject: [PATCH 4/4] qla2xxx: Handle incorrect entry_type entries Date: Thu, 27 Aug 2020 11:58:29 +0200 Message-Id: <20200827095829.63871-5-dwagner@suse.de> X-Mailer: git-send-email 2.16.4 In-Reply-To: <20200827095829.63871-1-dwagner@suse.de> References: <20200827095829.63871-1-dwagner@suse.de> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org It was observed on an ISP8324 16Gb HBA with fw=8.08.203 (d0d5) that pkt->entry_type was MBX_IOCB_TYPE/0x39 with an sp->type SRB_SCSI_CMD which is invalid and should not be possible. A careful code review of the crash dump didn't reveal any short comings. Reading the entry_type from the crash dump shows the expected value of STATUS_TYPE/0x03 but the call trace shows that qla24xx_mbx_iocb_entry() is used. One possible explanation is when pkt->entry_type is read it doesn't contain the correct information. That means the driver observes an data race by the firmware. Signed-off-by: Daniel Wagner --- drivers/scsi/qla2xxx/qla_isr.c | 28 ++++++++++++++++++++++++++-- 1 file changed, 26 insertions(+), 2 deletions(-) diff --git a/drivers/scsi/qla2xxx/qla_isr.c b/drivers/scsi/qla2xxx/qla_isr.c index b787643f5031..0c324e88b189 100644 --- a/drivers/scsi/qla2xxx/qla_isr.c +++ b/drivers/scsi/qla2xxx/qla_isr.c @@ -3392,6 +3392,31 @@ void qla24xx_nvme_ls4_iocb(struct scsi_qla_host *vha, sp->done(sp, comp_status); } +static void qla24xx_process_mbx_iocb_response(struct scsi_qla_host *vha, + struct rsp_que *rsp, struct sts_entry_24xx *pkt) +{ + srb_t *sp; + + sp = qla2x00_get_sp_from_handle(vha, rsp->req, pkt); + if (!sp) + return; + + if (sp->type == SRB_SCSI_CMD || + sp->type == SRB_NVME_CMD || + sp->type == SRB_TM_CMD) { + /* Some firmware version don't update the entry_type + * correctly. It was observed entry_type contained + * MBCX_IOCB_TYPE instead of the expected STATUS_TYPE + * for sp->type SRB_SCSI_CMD, SRB_NVME_CMD or + * SRB_TM_CMD. + */ + qla2x00_status_entry(vha, rsp, pkt); + return; + } + + qla24xx_mbx_iocb_entry(vha, rsp->req, (struct mbx_24xx_entry *)pkt); +} + /** * qla24xx_process_response_queue() - Process response queue entries. * @vha: SCSI driver HA context @@ -3499,8 +3524,7 @@ void qla24xx_process_response_queue(struct scsi_qla_host *vha, (struct abort_entry_24xx *)pkt); break; case MBX_IOCB_TYPE: - qla24xx_mbx_iocb_entry(vha, rsp->req, - (struct mbx_24xx_entry *)pkt); + qla24xx_process_mbx_iocb_response(vha, rsp, pkt); break; case VP_CTRL_IOCB_TYPE: qla_ctrlvp_completed(vha, rsp->req, -- 2.16.4