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: <1341409177.2507.117.camel@laptop>
Date:	Wed, 04 Jul 2012 15:39:37 +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 13:30 +0000, Liu, Chuansheng wrote:
> > Yuck.. and no. This makes sane things like early 8250 serial console less
> > reliable.
> Peter, could you share more? 

You avoid calling console write, this delays writing the output, this
delay might be infinite if the machine is sick enough.

Things like the 8250 early console don't take locks and are fine to
call.

> I took many time to dig out this issue.

Well, it was a known issue.. 

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

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