Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp6032214ybc; Wed, 27 Nov 2019 13:45:32 -0800 (PST) X-Google-Smtp-Source: APXvYqwpL42FG5SSs7djkdlCOyevIa2E48NCkzvKOgffDi2fVE0h9i7Bny+e4dpGCC7vrmzeS3eS X-Received: by 2002:a17:906:f109:: with SMTP id gv9mr51789683ejb.196.1574891132135; Wed, 27 Nov 2019 13:45:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574891132; cv=none; d=google.com; s=arc-20160816; b=lt+9HNsehBDHbB6Ees7CHvAsBxgTH4/vn3J/8LV3qOEimCPt/To8TR+QJefHl9b3M0 ofy1ENiXrVdRF686svPsITN7qGOMMjy8RdltIqOQQ4rKPn4o22tCN2dk3n/dt6RJNqb9 YGCs2BeT8YNhRDnsRgk6gRxe5RzsTtxHrXCKX/JvIULvbRQ+4Nqiap1cIVm2b65MLcoA Sq/vcYbZlepGQjpBMsDxt/Gsb9QEa1foFZ0CBoAWBYkSdTbdQGG3387i+UQ79thA1c3o DlzmB/1iGgIR+P30Ytf32iN2SrtEI8LY3Y32amIqLciddBb1SnOVxpPYo/ewWyXflgjX 4YPw== 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=paRHrn2vDROQhnne/PCTlWcOMG4KrRTDkgryev59HvU=; b=X0TZ7igKzDWz75T49XPiIZqpttUaHsd/6lknDEr3vYCQXgYZbP69O1DQHBj4G5ylDQ nBaNT+MmIx5xP1nReq6lkEMnBWzeqWmZhaZuuMjmWqBYRLHcXzI2I998Fhaw09N3PrZI mK4Uq1JKKekPl6SgZ6tkCzdTmon9IYAds2n19ynTRztw5TX1U4fXxFFyuAHzkuAJRFLf 8RbENNlkNvfAEA2PtG3IxBxCDtvr7oTTUoaTA6Hq0Qxfvq41/AJ8Wockp6u8B82fwy1m DL6/ELIx+7MOTPrDijIxKmJjqMVW5E6cGpYPhV8vyoRsioTkg9C+bAmavNn/WjLSeiFp sCxQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=pZTdpZN8; 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 f13si11754777edf.164.2019.11.27.13.45.08; Wed, 27 Nov 2019 13:45:32 -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=pZTdpZN8; 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 S1729813AbfK0VlA (ORCPT + 99 others); Wed, 27 Nov 2019 16:41:00 -0500 Received: from mail.kernel.org ([198.145.29.99]:48326 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728777AbfK0UmN (ORCPT ); Wed, 27 Nov 2019 15:42:13 -0500 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 1D67C21787; Wed, 27 Nov 2019 20:42:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1574887333; bh=jPgVZdWq1uxqLuuFB4zn5NW/loTd09gJehXLV22OFX8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=pZTdpZN86waNrmhU83ixguHqTSUPT4lgzkbgu/9P4QELczjRy3xVusXLCn8fr3xYb UnZGY61PfMga/aLrdA0GQUg3rMPUZAfM68zAqbCKsdw1ixF4hPontosGMisNRA78t4 iGQfivRMLe6XPU1SnLFN4NMJ/Bk1rOqmwdNX7mos= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Sam Bobroff , Michael Ellerman , Sasha Levin Subject: [PATCH 4.9 018/151] powerpc/eeh: Fix use of EEH_PE_KEEP on wrong field Date: Wed, 27 Nov 2019 21:30:01 +0100 Message-Id: <20191127203011.441618804@linuxfoundation.org> X-Mailer: git-send-email 2.24.0 In-Reply-To: <20191127203000.773542911@linuxfoundation.org> References: <20191127203000.773542911@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: Sam Bobroff [ Upstream commit 473af09b56dc4be68e4af33220ceca6be67aa60d ] eeh_add_to_parent_pe() sometimes removes the EEH_PE_KEEP flag, but it incorrectly removes it from pe->type, instead of pe->state. However, rather than clearing it from the correct field, remove it. Inspection of the code shows that it can't ever have had any effect (even if it had been cleared from the correct field), because the field is never tested after it is cleared by the statement in question. The clear statement was added by commit 807a827d4e74 ("powerpc/eeh: Keep PE during hotplug"), but it didn't explain why it was necessary. Signed-off-by: Sam Bobroff Signed-off-by: Michael Ellerman Signed-off-by: Sasha Levin --- arch/powerpc/kernel/eeh_pe.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/kernel/eeh_pe.c b/arch/powerpc/kernel/eeh_pe.c index 1abd8dd77ec13..eee2131a97e61 100644 --- a/arch/powerpc/kernel/eeh_pe.c +++ b/arch/powerpc/kernel/eeh_pe.c @@ -370,7 +370,7 @@ int eeh_add_to_parent_pe(struct eeh_dev *edev) while (parent) { if (!(parent->type & EEH_PE_INVALID)) break; - parent->type &= ~(EEH_PE_INVALID | EEH_PE_KEEP); + parent->type &= ~EEH_PE_INVALID; parent = parent->parent; } -- 2.20.1