Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp3884419pxv; Mon, 19 Jul 2021 11:04:51 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwz+oZfmeZNQHc15u5RdxI6PQCL5CL0yMAosdDW9Ik4GMDML/F1qXUVycwcxFmqqZGxqOjR X-Received: by 2002:a17:906:7190:: with SMTP id h16mr28544010ejk.251.1626717792057; Mon, 19 Jul 2021 11:03:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626717792; cv=none; d=google.com; s=arc-20160816; b=ett+C7UhEKOIjKa/sP9dAHwooADBfqkl5aVXZ92X4Bf8Ld7QiE+DS972NJ95KE4XgX LLg7chfqGe/dqOLyOEXeoAJUFUUXSg7HiqVR7xz9H2ixl1lKCU6hX5XBguf0a/HYPMsa Red5nPbUbbI77XNz3QrmsiFoWuN2FvCTxL1kDn59uHu/ieiyZ+beKUUE+oQfqx/J8OHs sEHjCACmOZhMH+PhhuCBTigerRz7PkTEUVUjBro6xx2Jt0bmK2VqZvYLzuWQnEValJM3 OXuoUjmFNCkSsUUKlhodud0qblcJVf98ggGj4h8GV0C6m6LLxmXa8NNYy/nXXPpf4hSO NlCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=yTPxHr5iDPFZAacWcPOlo5pArhQmBxca+Ml2wPHc8lw=; b=OqOVNRxhIXEXOyhqsaN6FZnMNnLiF0xMpQFiS4jR5RTSrmjjEV4fv7HwyUVx+fNzQe rwIZCZOeX7gWuya6R/aOyAWMWGkiLaC8a5d7rqA7BLcfTrggRbtWm+hpBnCRSml7DLr5 1aHpvGxMVnJr5TDl2kam4+T3ApDIogHWsv4epw1b3RkNm0yrv0V9b52Ph5FTq5TeT6gC GxhneerHZB4cQcKRJ1Q7PNc9VEYLHVn+rm19ZD8aH5W5tvXCVM/iYamP70Hf848EaeMl K7GpX5OFQDPJdH+DjbeGw1oCvmRkWkS19NN504yaQnfT6dI3fUcA0gg38d7pCXI9kvTy rVhw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=djADeYta; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bq16si22103037edb.303.2021.07.19.11.02.48; Mon, 19 Jul 2021 11:03:12 -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; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=djADeYta; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377425AbhGSRQ0 (ORCPT + 99 others); Mon, 19 Jul 2021 13:16:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:34378 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348103AbhGSPjy (ORCPT ); Mon, 19 Jul 2021 11:39:54 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 871C361242; Mon, 19 Jul 2021 16:19:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626711586; bh=XIV3LXYXWKRQG5f4IGBJbi06FZVjThgqYKV34LhbRhs=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=djADeYta9w2ToJuRtjGwrLF3dlADqU7NSgAU3KTlhn+R84MtrckySsCuBgAabGCwD CApjwSUAO3iiKFoAw0iOMO9aPUQGVnt+DW3wswbjNRn6npROW7ePCfM2JIYZIQt6w+ EGLMFHUGftJ1cMybUDdlrHxIRD16gfUFpjMcPyhg= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Justin Tee , James Smart , "Martin K. Petersen" , Sasha Levin Subject: [PATCH 5.12 058/292] scsi: lpfc: Fix "Unexpected timeout" error in direct attach topology Date: Mon, 19 Jul 2021 16:52:00 +0200 Message-Id: <20210719144944.430231790@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210719144942.514164272@linuxfoundation.org> References: <20210719144942.514164272@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: James Smart [ Upstream commit e30d55137edef47434c40d7570276a0846fe922c ] An 'unexpected timeout' message may be seen in a point-2-point topology. The message occurs when a PLOGI is received before the driver is notified of FLOGI completion. The FLOGI completion failure causes discovery to be triggered for a second time. The discovery timer is restarted but no new discovery activity is initiated, thus the timeout message eventually appears. In point-2-point, when discovery has progressed before the FLOGI completion is processed, it is not a failure. Add code to FLOGI completion to detect that discovery has progressed and exit the FLOGI handling (noop'ing it). Link: https://lore.kernel.org/r/20210514195559.119853-4-jsmart2021@gmail.com Co-developed-by: Justin Tee Signed-off-by: Justin Tee Signed-off-by: James Smart Signed-off-by: Martin K. Petersen Signed-off-by: Sasha Levin --- drivers/scsi/lpfc/lpfc_els.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/drivers/scsi/lpfc/lpfc_els.c b/drivers/scsi/lpfc/lpfc_els.c index 5c4172e8c81b..3b72aea9d15d 100644 --- a/drivers/scsi/lpfc/lpfc_els.c +++ b/drivers/scsi/lpfc/lpfc_els.c @@ -1175,6 +1175,15 @@ stop_rr_fcf_flogi: phba->fcf.fcf_redisc_attempted = 0; /* reset */ goto out; } + } else if (vport->port_state > LPFC_FLOGI && + vport->fc_flag & FC_PT2PT) { + /* + * In a p2p topology, it is possible that discovery has + * already progressed, and this completion can be ignored. + * Recheck the indicated topology. + */ + if (!sp->cmn.fPort) + goto out; } flogifail: -- 2.30.2