Received: by 10.213.65.68 with SMTP id h4csp434530imn; Tue, 13 Mar 2018 08:57:52 -0700 (PDT) X-Google-Smtp-Source: AG47ELuYgZeF5TpHFErO1JKrGxX/2iSKEIXfcuIHn8TyVCff/9S1KACl1q4fiU/l8ZaVyEX0w3ie X-Received: by 2002:a17:902:1c5:: with SMTP id b63-v6mr972562plb.311.1520956672179; Tue, 13 Mar 2018 08:57:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1520956672; cv=none; d=google.com; s=arc-20160816; b=O7NBddqbPQU1L/JPEArtRlzGmIpJO0SMXTAi+18jSSnzjHvD9P0ehCEnkw8vtGkOop cxT1iCEf/bvlcaXDkf78tKJiZTHrtTWEo5s0pgu94lvszEmNet1RaQQW2xVDZon3gFJ4 SNui/QNq/JMqUKHZh4f5j9ahEXP/Jqqs2VJJgBs0RyOS/ZOhSMNvP31bx68UYYnQXR7+ Zk+bqUNjaxQi3U2JW9NozbEt2VleT2tXYfa8H913SOHnUd3d7bWXX0N+xm2ZtzERn8Y1 oAghe30pAxDbi7H6hDRopXn0EkvNt+1koKZgeEnWSW07tmAfV9ArCm3mfS25b5G/hcjq nwlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=+8xFpde2mBouwcTbMpS+i2eo7IA8KZg8mE92Z/ZXgJk=; b=X55YThJsXmlMNRrJ5sPUpn5JFOzR6woYMv8k7M/OF7iC56K69Ca8gBzhxFtiJP9xX2 lM3nRflkqqr0Ch1u9QZ3kj7HtuQ/EUOa+frQCusvcWO6K2hy46K+uI0xtGoXVgt7FIsB 2ZS4Ghs5xBwMx3pZWYnkcINfvTaSvl5ghU3pAZTTmRgt39CTmL7BzkUvHvnzTFv0dMP0 7qRtc1LpiIE31WbO8YqlFYH0PkBfEWTuxTMIBpmRuLVMzSH8+XcpBvr8EWahrhZ5TbVE 4RWu79wneLq4SVU89ThFLBSe+gsob5KlccDem3P+ORLShRmcPOMMOQXxXhsMm88V3mug Dr8Q== ARC-Authentication-Results: i=1; mx.google.com; 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 t18si309729pfg.246.2018.03.13.08.57.37; Tue, 13 Mar 2018 08:57:52 -0700 (PDT) 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; 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 S934627AbeCMPiz (ORCPT + 99 others); Tue, 13 Mar 2018 11:38:55 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:35086 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933977AbeCMPix (ORCPT ); Tue, 13 Mar 2018 11:38:53 -0400 Received: from localhost (LFbn-1-12258-90.w90-92.abo.wanadoo.fr [90.92.71.90]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 285CFF73; Tue, 13 Mar 2018 15:38:52 +0000 (UTC) From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Justin Chen , Florian Fainelli , linux-mips@linux-mips.org, James Hogan Subject: [PATCH 4.14 078/140] MIPS: BMIPS: Do not mask IPIs during suspend Date: Tue, 13 Mar 2018 16:24:41 +0100 Message-Id: <20180313152503.380862971@linuxfoundation.org> X-Mailer: git-send-email 2.16.2 In-Reply-To: <20180313152458.201155692@linuxfoundation.org> References: <20180313152458.201155692@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.14-stable review patch. If anyone has any objections, please let me know. ------------------ From: Justin Chen commit 06a3f0c9f2725f5d7c63c4203839373c9bd00c28 upstream. Commit a3e6c1eff548 ("MIPS: IRQ: Fix disable_irq on CPU IRQs") fixes an issue where disable_irq did not actually disable the irq. The bug caused our IPIs to not be disabled, which actually is the correct behavior. With the addition of commit a3e6c1eff548 ("MIPS: IRQ: Fix disable_irq on CPU IRQs"), the IPIs were getting disabled going into suspend, thus schedule_ipi() was not being called. This caused deadlocks where schedulable task were not being scheduled and other cpus were waiting for them to do something. Add the IRQF_NO_SUSPEND flag so an irq_disable will not be called on the IPIs during suspend. Signed-off-by: Justin Chen Fixes: a3e6c1eff548 ("MIPS: IRQ: Fix disabled_irq on CPU IRQs") Cc: Florian Fainelli Cc: linux-mips@linux-mips.org Cc: stable@vger.kernel.org Patchwork: https://patchwork.linux-mips.org/patch/17385/ [jhogan@kernel.org: checkpatch: wrap long lines and fix commit refs] Signed-off-by: James Hogan Signed-off-by: Greg Kroah-Hartman --- arch/mips/kernel/smp-bmips.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) --- a/arch/mips/kernel/smp-bmips.c +++ b/arch/mips/kernel/smp-bmips.c @@ -168,11 +168,11 @@ static void bmips_prepare_cpus(unsigned return; } - if (request_irq(IPI0_IRQ, bmips_ipi_interrupt, IRQF_PERCPU, - "smp_ipi0", NULL)) + if (request_irq(IPI0_IRQ, bmips_ipi_interrupt, + IRQF_PERCPU | IRQF_NO_SUSPEND, "smp_ipi0", NULL)) panic("Can't request IPI0 interrupt"); - if (request_irq(IPI1_IRQ, bmips_ipi_interrupt, IRQF_PERCPU, - "smp_ipi1", NULL)) + if (request_irq(IPI1_IRQ, bmips_ipi_interrupt, + IRQF_PERCPU | IRQF_NO_SUSPEND, "smp_ipi1", NULL)) panic("Can't request IPI1 interrupt"); }