Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp26113imu; Thu, 8 Nov 2018 14:07:39 -0800 (PST) X-Google-Smtp-Source: AJdET5djzE3vLpn0nv6qX2T/CmW3UFLOrnzVgejRo9D0dIUvyJJ6+l27o57BFANBN15ad6lQd+gW X-Received: by 2002:a17:902:4083:: with SMTP id c3-v6mr6339319pld.181.1541714858990; Thu, 08 Nov 2018 14:07:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541714858; cv=none; d=google.com; s=arc-20160816; b=ZKV10DHs9/CN9Ku3N4zNhRWs6PPOgSkqHzWtRahodCHs9Yc/7YOMdfStge6Sa0yWZB 9mRZ/GzydX5zvOCjOTHW4pKStzscJUM+DmSEV6a+okDJDtKyI7bAenpwcvuYj1wEgzc7 tvR1TOLlajnvc7YQdeQLu4AzDO4R6uuU8yPr3OXLpZTd98XuMVgXmncEegiVO0dkAaWc KNbuqk6HMTTRTHKeRwd+wD9lqkvXZZyBtqe6ph6iIt6URXVPM96+mi8MsO3DalUX7TOo aBkyIDyNWIjnMWQFNezLxtJMrg6/00sK3LwzJT5NqG4k+SOkN96olrxdtSy/xOb8onip ShJA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=nV5pkGsIYgfMgPAwoebuzWdS2n5erOna4eMsEhhf5tM=; b=saHtoKbsEjZ3e0LUM1Ha0LRG2QrILeEPQtwOBEy1/oRek36uJLG9phXlp44yS26vW0 pj2+inIxRFpc/ANFevSK9vDxKbwHc57PyVoR8hg6nE9XGDoivMJfA45FuR6US2mgYU01 RhaLxTOm2SOmk8Y7Agxpebg8ClvCx5KQPktuIG2DlnXc8dine7rFblF0Zv00/EoGbwB+ GGN6jvbC2fUYMDIA7j23CQ+4Zee+N5oYJFv4xAhUgI+THErJ/4HOVK1nDMcM7Q9I+PJc p1FWDjmzizcO/wHtaRzJucMB8jdIHO6GzhKw0/RWVWAEuMZ7dBRMKn9eMAsEiQdyDV2Q p/+g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=YHHVZz9K; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b76-v6si5966328pfb.89.2018.11.08.14.07.22; Thu, 08 Nov 2018 14:07:38 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=YHHVZz9K; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731139AbeKIHnV (ORCPT + 99 others); Fri, 9 Nov 2018 02:43:21 -0500 Received: from mail.kernel.org ([198.145.29.99]:35700 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727203AbeKIHnT (ORCPT ); Fri, 9 Nov 2018 02:43:19 -0500 Received: from localhost (unknown [208.72.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6935A20844; Thu, 8 Nov 2018 22:05:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541714749; bh=3D0skHJJKSVT+B2QOIRonhUnU6RVO5w5wVieVhBhn3c=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=YHHVZz9K2yY4z4qS1TpH6Dway0k3w93Q6IfhNwYmV+XjeJUhAo03EZHietMhrbkrD 5frBtzG6yfbm7f7MzGELDI5n1JOr1ADg8+mz8aroOnlhNZYl8M7aFhJZ+UrSkvQGHJ SKGJQupePwCmvTax+r3zW/kFY0xyrdNYijVsUjso= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Gal Pressman , Saeed Mahameed , Sasha Levin Subject: [PATCH 4.9 075/171] net/mlx5: Fix driver load error flow when firmware is stuck Date: Thu, 8 Nov 2018 13:50:45 -0800 Message-Id: <20181108215132.965954520@linuxfoundation.org> X-Mailer: git-send-email 2.19.1 In-Reply-To: <20181108215127.257643509@linuxfoundation.org> References: <20181108215127.257643509@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ [ Upstream commit 8ce59b16b4b6eacedaec1f7b652b4781cdbfe15f ] When wait for firmware init fails, previous code would mistakenly return success and cause inconsistency in the driver state. Fixes: 6c780a0267b8 ("net/mlx5: Wait for FW readiness before initializing command interface") Signed-off-by: Gal Pressman Signed-off-by: Saeed Mahameed Signed-off-by: Sasha Levin --- drivers/net/ethernet/mellanox/mlx5/core/main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/mellanox/mlx5/core/main.c b/drivers/net/ethernet/mellanox/mlx5/core/main.c index 6698a3a07406..d676088512cf 100644 --- a/drivers/net/ethernet/mellanox/mlx5/core/main.c +++ b/drivers/net/ethernet/mellanox/mlx5/core/main.c @@ -957,7 +957,7 @@ static int mlx5_load_one(struct mlx5_core_dev *dev, struct mlx5_priv *priv, if (err) { dev_err(&dev->pdev->dev, "Firmware over %d MS in pre-initializing state, aborting\n", FW_PRE_INIT_TIMEOUT_MILI); - goto out; + goto out_err; } err = mlx5_cmd_init(dev); -- 2.17.1