[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <27240C0AC20F114CBF8149A2696CBE4A10CA93@SHSMSX101.ccr.corp.intel.com>
Date: Wed, 4 Jul 2012 14:46:41 +0000
From: "Liu, Chuansheng" <chuansheng.liu@...el.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC: "'linux-kernel@...r.kernel.org' (linux-kernel@...r.kernel.org)"
<linux-kernel@...r.kernel.org>, "kay@...y.org" <kay@...y.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"mingo@...e.hu" <mingo@...e.hu>
Subject: RE: [PATCH] printk: fixing the deadlock when calling printk in nmi
handle
> > I took many time to dig out this issue.
>
> Well, it was a known issue..
Still feel unfair :)
If this is a known issue that calling printk is not safe in nmi handler,
Why not defense it like this patch before real solution coming out?
Thanks.
Powered by blists - more mailing lists