Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp3832283pxv; Mon, 19 Jul 2021 09:47:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyFpLdPYgk5tmx25KqIfs/SfGlymNabfn2ValAHW8YZYe42nyx9T4oOrjXlCwsX0K4WLe/h X-Received: by 2002:a17:906:cb8b:: with SMTP id mf11mr28021765ejb.297.1626713276476; Mon, 19 Jul 2021 09:47:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626713276; cv=none; d=google.com; s=arc-20160816; b=sCmq9ZhbhtJCe7x68YVoMUdVr4N9+UshYF2u0V4ZX158T4eKABKvYNSQ81cRy4h6Ip sfZ70PXRZeU1iOYJPuF4h43TSGl0UPk7txAUqomDvHRh5JYKikyTX31Dth1yBbzTJRBV BPpWunzvnADh3UsMlp0PmmrA9xoMd2XP4VdW6SzHcmDN8dXYo3Gwx/tVmi89EeI/HcI0 Oa/Er9Jyn/+w5CJxlruZoeuTIKbRxd6CGdntx3/ghKjd3BChAeVruj5auIkDN1Alhln5 /GK5KAetlYKnmVX3vKV3gP6A0yzA1u1ucvi8+jdUTsoNNAPw8bZuVfnmGv0HPUMjaxCJ 3KXA== 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=fTJEchIaSkZaOyntmD+Kz3GwwEz22mc/oQk1yfrKprA=; b=UBXfAhZhQ52RBkd4KEe6I0uS5NIPAijGNuF5ySjNZo3AP31LCuQON7gSv4TZL2ZcEE EkJ3PzQLpzUF5+O4b++wJi89DqNjU9Mt/+4Uthvv1mKXRdfBk8QnLPNg+Glv3LdyzUzi WkLa2FxQPN7xnCLorD3f/OzVt3GimZ9l/Y8f8xcsdPV3idM97ikfD9iYTUpkGZkEsveM l9LF+mM18V0Z/nl+dUNcE00k8FOBW8cylWzXwpkYZp4AEZ7r/5eByKuhHSxFw7XiaRUf nhKhMSKE5m9OfUiB2teEPnSGlIw2dWaVoFmqQWy644zaPjF5ytOEoP8Drd10I7b3wTzL ULTw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=PYbXMHMf; 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 b1si26923786ejb.152.2021.07.19.09.47.33; Mon, 19 Jul 2021 09:47:56 -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=PYbXMHMf; 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 S243395AbhGSQFr (ORCPT + 99 others); Mon, 19 Jul 2021 12:05:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:38868 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344264AbhGSPGZ (ORCPT ); Mon, 19 Jul 2021 11:06:25 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 8EE096121F; Mon, 19 Jul 2021 15:46:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626709608; bh=0LIP5qKIYPKgyLpH3K4NFeCwIuVJD7wjkrRIpCICnDU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=PYbXMHMfaYyk8VqgAnjrnhl6Q0MEBy4dLwRExH3PaUIHI1iWxDw2263D1JL0Vu8QA 1Z3z4onAoyKzh1HXQEHEaDe3nlg/F5RD/PyjTi/MNZV4Guh552SjB91nAm7SLyBrkL WNne1AgYubZtNFeBAkvb+F0yKhGO624BA1Uv2W58= 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.4 020/149] scsi: lpfc: Fix "Unexpected timeout" error in direct attach topology Date: Mon, 19 Jul 2021 16:52:08 +0200 Message-Id: <20210719144906.253245006@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210719144901.370365147@linuxfoundation.org> References: <20210719144901.370365147@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 4e994a693e3f..2040affa0887 100644 --- a/drivers/scsi/lpfc/lpfc_els.c +++ b/drivers/scsi/lpfc/lpfc_els.c @@ -1179,6 +1179,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