Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp126844ybm; Tue, 26 May 2020 12:26:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyyIOQLQYuti9fpsGLEjHgI88h2Fr06TTvDc3/i32Fsx3WvTe7gWxFZaPX88mMWEVYnYitF X-Received: by 2002:a05:6402:1447:: with SMTP id d7mr22239170edx.367.1590521198364; Tue, 26 May 2020 12:26:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590521198; cv=none; d=google.com; s=arc-20160816; b=B7JhzhkIgrZsO2F1cuN7XzGlt6Z23t4wt7+BsCRSco+RYyKgJJ0NesyiWcLo6birXq qXiGnkotLJfxt+PidaUGC5gTISW3yc5fWalJH21xHDhS7MyRuWuJQV1SBec3BV2h9XEG ensoAuSVpFx0BJ78Y35UOQIfbQjFTB5EgedwC6iRg7UurINqbmCAn6ngupnd4zrY00hw 4R9ICaIb0pUlNcj1gjQmhHZmBY0t36+zZiUA+OM0FPpjIvI0+qUNcjORc2Ib8XqbSA14 V/tYArtYj3VAEGOl7ig123Howg1tTVYdPnJfVrDEwhx+0WnsxWfDGS8pbQ9N6D6/XHUv a9aQ== 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=7S/i77hIaEG77C0PJu8y3qAVD+TG5aQM54qBRPGcOec=; b=c2+TMpL1Tcq4OBkboVNflmg9rO4O4nsL3It60kpDs+xHPvdgRJ6NLc947V+Jhu354P yXNiLENwGDkJPpPz7Wk/Jx4KtFgFVktTCYuU3higbI++uB+wBF6XtO7WggjIo8CGzckC zuHSt2K3qa8MskJGF3i6iWWPgEY3rcQmJNGlYT4bfuNpC3LkxRv65j2l0VUXZwceCoJP i9ZvtpFtMLbdOmVKvLsWN5ob3ucghtj82TkOahRtQzXWTotRSP4FY32gr7fE5KloMxxX AoB3E2FBVm9fqMwRtXH7zKyugMpZ6C2GRwtCEyzPvexEq7wD9SVkXem7ic7MsJVPD78p 2J6Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=cZxOUDHs; 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 se22si385275ejb.725.2020.05.26.12.26.14; Tue, 26 May 2020 12:26:38 -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=@kernel.org header.s=default header.b=cZxOUDHs; 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 S2404149AbgEZTXf (ORCPT + 99 others); Tue, 26 May 2020 15:23:35 -0400 Received: from mail.kernel.org ([198.145.29.99]:38092 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391818AbgEZTJC (ORCPT ); Tue, 26 May 2020 15:09:02 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (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 33C8D20776; Tue, 26 May 2020 19:09:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1590520141; bh=2zQbOFk7UokBnaJoU3QOA1uEDUj2qmeb2ZaGzIM4pvA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=cZxOUDHsIs0pd1dXDqk7hWQjjHiEEh8+1HiPE79R4xnVdGiryDgPIhkLg7AF07/14 jPslJpCRm546M5ZUNk7VrkY/j5l3f3ottlEu7ZY+iigIb/+4VrfW84RFN07C5O1PyZ sul8lTtYp3gbnbkZ/n8IJQpnveNeiaIDNBaJ0tBU= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Juliet Kim , "David S. Miller" , Sasha Levin Subject: [PATCH 5.4 034/111] ibmvnic: Skip fatal error reset after passive init Date: Tue, 26 May 2020 20:52:52 +0200 Message-Id: <20200526183936.067512660@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200526183932.245016380@linuxfoundation.org> References: <20200526183932.245016380@linuxfoundation.org> User-Agent: quilt/0.66 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 From: Juliet Kim [ Upstream commit f9c6cea0b38518741c8dcf26ac056d26ee2fd61d ] During MTU change, the following events may happen. Client-driven CRQ initialization fails due to partner’s CRQ closed, causing client to enqueue a reset task for FATAL_ERROR. Then passive (server-driven) CRQ initialization succeeds, causing client to release CRQ and enqueue a reset task for failover. If the passive CRQ initialization occurs before the FATAL reset task is processed, the FATAL error reset task would try to access a CRQ message queue that was freed, causing an oops. The problem may be most likely to occur during DLPAR add vNIC with a non-default MTU, because the DLPAR process will automatically issue a change MTU request. Fix this by not processing fatal error reset if CRQ is passively initialized after client-driven CRQ initialization fails. Signed-off-by: Juliet Kim Signed-off-by: David S. Miller Signed-off-by: Sasha Levin --- drivers/net/ethernet/ibm/ibmvnic.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/net/ethernet/ibm/ibmvnic.c b/drivers/net/ethernet/ibm/ibmvnic.c index e1ab2feeae53..aaa03ce5796f 100644 --- a/drivers/net/ethernet/ibm/ibmvnic.c +++ b/drivers/net/ethernet/ibm/ibmvnic.c @@ -2086,7 +2086,8 @@ static void __ibmvnic_reset(struct work_struct *work) rc = do_hard_reset(adapter, rwi, reset_state); rtnl_unlock(); } - } else { + } else if (!(rwi->reset_reason == VNIC_RESET_FATAL && + adapter->from_passive_init)) { rc = do_reset(adapter, rwi, reset_state); } kfree(rwi); -- 2.25.1