Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp4766863pxj; Wed, 9 Jun 2021 01:04:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxL4SqIiUtYpCP+13VC6Emg3BmVlGcJxn9olEclcuK6ehqMKmP1as7MylzMwjhr4LbgurOc X-Received: by 2002:a50:ec08:: with SMTP id g8mr30292923edr.376.1623225851065; Wed, 09 Jun 2021 01:04:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623225851; cv=none; d=google.com; s=arc-20160816; b=RtUTmcxgss9UOFEUAVDco4FuV2E6JieGWmud/y8TNKThCvA1Gr9efNBc5C++LzKKPV w2QhmkUOL1sj/+/aFTfW/25jA04bAD1u5u4hZs00W+83cbAHceqIPAL3B8GeMjDgw5n7 YYebdf7bMLQxpsX8bS2VDPmITzGKvUsPUYhJJHvkyTQkVcsJ/SaaRuAcpkIJhUT4IIlX n/DEm3x4d7PSSmYr568t7J5RdH/CuleaTFeTGtOJrbjp5e1aIoMhvwL0QIhn4KfhvQ28 6tJ2chEiArpSmoyDSHK2x7rpFmGsWHJVLL2fVOhPDW6rm+niuZFta2jLhafLVJRbFMO/ qkLQ== 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=Nuj/ohAzNyIwVWxcdK8u63hen9KUcFr3GDQ3nes3qPs=; b=wP3DDPMqLiN156osBo9k4TzsUssOj7ENn2OxazcnDt1Y9K43krNwopZoM7WTON0trg cDVVDTPKHBE2T1uTvJp4g2bTuV7cKndIOfVECbqnzxjrSIJcP1epwqOdSH2Arz3s+BBZ YV9ikvK5tZXvx5L7ZWaVKBC6fcQcsJa5pWKrB5X2c67xGsj+rBRiQ/ARvO/A+U4JXMne 7Hf8gBCQpGbu1UlS8Dnbv7n2+s1hcPHgLR81Bh44EUkK0ORf0ma8HEQsVqev9DRGW/WS VtgpNgsfNr40CAtWeCATxjDKoXlB7J/pZ6/wbW5D1y9L6gYSRFclwfuIqKEsJbdg7v3k toKw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="P2T6ikE/"; 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 m26si2152734edp.313.2021.06.09.01.03.48; Wed, 09 Jun 2021 01:04:11 -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="P2T6ikE/"; 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 S235251AbhFHTPf (ORCPT + 99 others); Tue, 8 Jun 2021 15:15:35 -0400 Received: from mail.kernel.org ([198.145.29.99]:48710 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237794AbhFHTFZ (ORCPT ); Tue, 8 Jun 2021 15:05:25 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 5C54061449; Tue, 8 Jun 2021 18:46:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1623177988; bh=Saa7yUtcScnOSYHA+UPX6fJ+T9gBQ6O+JceFWKHjKYM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=P2T6ikE/00WnSAtjnffd++Wuw/6BGiD2VBs/JjgAgVjiB6/EE4lw7EF7wytP9SoYH uGd1ucH0uHbJoAcFFvW9SagaXXGBIlBi3ki/gxMTKyGTRNJPGzUpbDHGOpL79xRV7D ngiEfm+uuv3tPGgZ8Dz+Ee0kjRIQOC/SAJbZ/B/w= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Moshe Shemesh , Tariq Toukan , Saeed Mahameed , Sasha Levin Subject: [PATCH 5.12 035/161] net/mlx5: Check firmware sync reset requested is set before trying to abort it Date: Tue, 8 Jun 2021 20:26:05 +0200 Message-Id: <20210608175946.642052789@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210608175945.476074951@linuxfoundation.org> References: <20210608175945.476074951@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: Moshe Shemesh [ Upstream commit 5940e64281c09976ce2b560244217e610bf9d029 ] In case driver sent NACK to firmware on sync reset request, it will get sync reset abort event while it didn't set sync reset requested mode. Thus, on abort sync reset event handler, driver should check reset requested is set before trying to stop sync reset poll. Fixes: 7dd6df329d4c ("net/mlx5: Handle sync reset abort event") Signed-off-by: Moshe Shemesh Reviewed-by: Tariq Toukan Signed-off-by: Saeed Mahameed Signed-off-by: Sasha Levin --- drivers/net/ethernet/mellanox/mlx5/core/fw_reset.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/net/ethernet/mellanox/mlx5/core/fw_reset.c b/drivers/net/ethernet/mellanox/mlx5/core/fw_reset.c index f9042e147c7f..ee710ce00795 100644 --- a/drivers/net/ethernet/mellanox/mlx5/core/fw_reset.c +++ b/drivers/net/ethernet/mellanox/mlx5/core/fw_reset.c @@ -354,6 +354,9 @@ static void mlx5_sync_reset_abort_event(struct work_struct *work) reset_abort_work); struct mlx5_core_dev *dev = fw_reset->dev; + if (!test_bit(MLX5_FW_RESET_FLAGS_RESET_REQUESTED, &fw_reset->reset_flags)) + return; + mlx5_sync_reset_clear_reset_requested(dev, true); mlx5_core_warn(dev, "PCI Sync FW Update Reset Aborted.\n"); } -- 2.30.2