[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1341410957.2507.120.camel@laptop>
Date: Wed, 04 Jul 2012 16:09:17 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: "Liu, Chuansheng" <chuansheng.liu@...el.com>
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
On Wed, 2012-07-04 at 15:39 +0200, Peter Zijlstra wrote:
> > Anyway, in nmi handler, calling printk is dangerous. This patch is for this case.
>
> But its ugly and decreases reliability.. Your 'solution' is to
> basically ignore serialization and pray, that's not a solution, that's
> gambling.
If you want to fix it, do something like:
http://marc.info/?l=linux-kernel&m=132446646923333
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists