Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751597AbdF1JUE (ORCPT ); Wed, 28 Jun 2017 05:20:04 -0400 Received: from [140.206.112.106] ([140.206.112.106]:4921 "EHLO mail2012.asrmicro.com" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751567AbdF1JTq (ORCPT ); Wed, 28 Jun 2017 05:19:46 -0400 X-Greylist: delayed 904 seconds by postgrey-1.27 at vger.kernel.org; Wed, 28 Jun 2017 05:19:37 EDT From: Qiao Zhou To: , , , , , , , , , CC: Qiao Zhou Subject: [PATCH] *** arm64: traps: disable irq in die() *** Date: Wed, 28 Jun 2017 17:04:11 +0800 Message-ID: <1498640652-23338-1-git-send-email-qiaozhou@asrmicro.com> X-Mailer: git-send-email 2.7.4 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.1.50.16] X-ClientProxiedBy: mail2012.asrmicro.com (10.1.24.123) To mail2012.asrmicro.com (10.1.24.123) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 620 Lines: 17 I met several cases that die() is interrupted once irq is unlocked, on our platform which has multiple cpus, and enables panic_on_oops. It deadlock in some schedule related code, and hard-lockup is triggered. So the first criminal field is gone. So I want to protect the whole flow of die() from irq, and let the panic flow execute correctly. Not sure this patch is suitable or there is better way to solve it. Please help to give some comments. Thanks in advance. Qiao Zhou (1): arm64: traps: disable irq in die() arch/arm64/kernel/traps.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) -- 2.7.4