linux-kernel - RE: [PATCH] printk: fixing the deadlock when calling printk in nmi handle

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1341413431.2507.124.camel@laptop>
Date:	Wed, 04 Jul 2012 16:50:31 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
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 14:46 +0000, Liu, Chuansheng wrote:
> > > 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?

Why replace one broken thing with another broken thing?

--
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/