Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp2277269pxb; Mon, 11 Jan 2021 05:52:40 -0800 (PST) X-Google-Smtp-Source: ABdhPJykXqkPZ0zCCHtpJbbh/Bwcnv2yZWXTbTfKdKGdqad/LDrK4DAktJ59U2/2BzSNzWcauF1e X-Received: by 2002:a17:906:b7cc:: with SMTP id fy12mr11186133ejb.390.1610373160664; Mon, 11 Jan 2021 05:52:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610373160; cv=none; d=google.com; s=arc-20160816; b=Zxd6jR4UrDOBD6wrh0Y+LVQbNvCBN00BqzMdMh8G+zn1t8pczb3/l0+5wOR5WEIKHH I6j/oXl+1OxdcFbfLxmnf5TxKk0mXLBBUTfIwKJt3fjMV5MdTbsSJBNL/FnFprkWarAS p8dfCYiE01Kg7HdismJNSXLtnWLNx97OCckM6/A1Y54YpN3IPNK7FnksHDcQ9vmow0Xt MvOPMkoFM63EovDNszvhBqatrs50EDrPb6vHiNsQvnUGYqYsA0UImGCJqGbj3hTJzafz +TesyFLObFPgd5Ch75gobNT2gEG4uY/1+cBYkI2wyB+0kAoucxB1IQ/KvzwuefmUhunk jqwQ== 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=Q8KVp069QXkptJVgtH0lzp77bwqfAdOiMatF9xffQas=; b=ElqmpX4qKfcuwqrz94o2AGpa5ftXDM/0Q256KA1Qmb7jxFqc1XwluDESlJO+lT59Zg 83HYG3s/9gOHh6WfzxoNgXSFKazYW5cIKCIslYUaGln1jrYHgoTavUh1GP/jVUeh5hz3 xOFWKbKK5zFCVWNhxa0Kwf0QeEmjzsb0UdU7IAtrSkrj526wWBMzlVMITGr4N3nedgm3 tyNM/0NfGTL3xD07TNq/EAgvMtumb1yPGHKLjTml2++Xmyx7kXc9tOAf9K+9qyk/o/hW PrI0EBvZCieigTc30M2gereB53eXAv3JViV+cNADrKeB9PSk8nA4B6mrE1sw4464AVO0 TsDA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Y+ikz1aA; 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 j20si6761072ejt.403.2021.01.11.05.52.15; Mon, 11 Jan 2021 05:52:40 -0800 (PST) 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=Y+ikz1aA; 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 S1731161AbhAKNsH (ORCPT + 99 others); Mon, 11 Jan 2021 08:48:07 -0500 Received: from mail.kernel.org ([198.145.29.99]:57080 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731159AbhAKNKW (ORCPT ); Mon, 11 Jan 2021 08:10:22 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 1995D227C3; Mon, 11 Jan 2021 13:10:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1610370606; bh=hLLzEPQY8VAY5q5euyvIb5OFtst85ZLzRA/q33b3Yfw=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Y+ikz1aA3fIbsssvW68Tmz+2e1npQAPNhdObwvDYoInMv5Vbyl+BuXvnTtHqekihN fuVeqHt0K3ecfffy/TKFOe89JuLPpYoWrp4qzQwAGG/2KvS3FAbqU4kuPkdpwL9FlA piPrrJ9BsHbq4UCpy2MCV/QooHmaz/XYIoZDsz18= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Lijun Pan , Jakub Kicinski Subject: [PATCH 5.4 19/92] ibmvnic: continue fatal error reset after passive init Date: Mon, 11 Jan 2021 14:01:23 +0100 Message-Id: <20210111130040.084133057@linuxfoundation.org> X-Mailer: git-send-email 2.30.0 In-Reply-To: <20210111130039.165470698@linuxfoundation.org> References: <20210111130039.165470698@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: Lijun Pan [ Upstream commit 1f45dc22066797479072978feeada0852502e180 ] Commit f9c6cea0b385 ("ibmvnic: Skip fatal error reset after passive init") says "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." Even with this commit, we still see similar kernel crashes. In order to completely solve this problem, we'd better continue the fatal error reset, capture the kernel crash, and try to fix it from that end. Fixes: f9c6cea0b385 ("ibmvnic: Skip fatal error reset after passive init") Signed-off-by: Lijun Pan Link: https://lore.kernel.org/r/20201219214034.21123-1-ljp@linux.ibm.com Signed-off-by: Jakub Kicinski Signed-off-by: Greg Kroah-Hartman --- drivers/net/ethernet/ibm/ibmvnic.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) --- a/drivers/net/ethernet/ibm/ibmvnic.c +++ b/drivers/net/ethernet/ibm/ibmvnic.c @@ -2152,8 +2152,7 @@ static void __ibmvnic_reset(struct work_ rc = do_hard_reset(adapter, rwi, reset_state); rtnl_unlock(); } - } else if (!(rwi->reset_reason == VNIC_RESET_FATAL && - adapter->from_passive_init)) { + } else { rc = do_reset(adapter, rwi, reset_state); } kfree(rwi);