Received: by 10.213.65.68 with SMTP id h4csp528540imn; Fri, 16 Mar 2018 10:29:07 -0700 (PDT) X-Google-Smtp-Source: AG47ELvaObia9nNkS5+SqeN+AO/wA6JvaSdNOMDvB2fJbk+Rn8UEkgMwrpeQqiDrxXlWp2PeGqc3 X-Received: by 10.99.117.26 with SMTP id q26mr2045987pgc.169.1521221347612; Fri, 16 Mar 2018 10:29:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521221347; cv=none; d=google.com; s=arc-20160816; b=lmekqEpU1NqnBqOkJyH74aDzzDjS3X5mxVkdgg0k+ZdkBQJsoCXklTa/OabX9LELKR o2lgk1KpJLcRSBN9Ht4MuzVvyv0wZ84MEzZRBrC7n51w0+WnNSGgwGeZEdyFulj0sHWT C8ulFa0Q0oicDopLxGZSVowRg0c5xGGTpxVuvriZzuLomegPOGIT7lDZmjUAY5LHpd2e NqbAqQjnmiu4p89ExDCAYnqgsMpVYabzCrhpFt5+P5GyngujET6VPYCxOdYabOp/VFf3 hbMqebQq0b9g6/aaspINPCgJyaQVAdh5B80EXfWU9G91kZXReBqhEBx+KWMnm1B8FVId q40w== 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=fp2lqWDbbvCkBsbcLc20//jC/YozAMkc3BVRBftfvjU=; b=fZd+6SFRqw6WBFh3fmPktTq2ygEdU++DrN3lVhiSXU494Bg6HpEct6VShOlkJ4adrX vNfHozQpD/4TScJEcahre2ZViK3iGJAW6E+i58wbj9xN3GqlsWZekfZ3aWgQa3wHcgf3 n0j34xTI/nzaOie90lCjGxYNTUp5yQY9XJFUvcqbcMDBhtnbHCnq8t+sNOE2NUabmHJP 3kEFJ4ZqXPOxarCou3S3NBFviMYlDcLNf+pZJ5NR/R7MEkxhc9LTmsZbc/3R0sKzwCos jFd55IDr2q4HSodigobZIqurS0GN+SmHRo/ttWtU3zyHNETNqWQ2Nj1KRA4KZHgHn4dB xdnQ== 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 x5si5186539pgb.365.2018.03.16.10.28.53; Fri, 16 Mar 2018 10:29:07 -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 S932841AbeCPP2Y (ORCPT + 99 others); Fri, 16 Mar 2018 11:28:24 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:35010 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752678AbeCPP2V (ORCPT ); Fri, 16 Mar 2018 11:28:21 -0400 Received: from localhost (LFbn-1-12247-202.w90-92.abo.wanadoo.fr [90.92.61.202]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 36B911252; Fri, 16 Mar 2018 15:28:20 +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.4 13/63] MIPS: BMIPS: Do not mask IPIs during suspend Date: Fri, 16 Mar 2018 16:22:45 +0100 Message-Id: <20180316152301.507392406@linuxfoundation.org> X-Mailer: git-send-email 2.16.2 In-Reply-To: <20180316152259.964532775@linuxfoundation.org> References: <20180316152259.964532775@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.4-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 @@ -166,11 +166,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"); }