[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1498640652-23338-1-git-send-email-qiaozhou@asrmicro.com>
Date: Wed, 28 Jun 2017 17:04:11 +0800
From: Qiao Zhou <qiaozhou@...micro.com>
To: <catalin.marinas@....com>, <will.deacon@....com>,
<mark.rutland@....com>, <suzuki.poulose@....com>,
<mingo@...nel.org>, <andre.przywara@....com>,
<marc.zyngier@....com>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <zhizhouzhang@...micro.com>
CC: Qiao Zhou <qiaozhou@...micro.com>
Subject: [PATCH] *** arm64: traps: disable irq in die() ***
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
Powered by blists - more mailing lists