linux-kernel - Re: deadlock caused by printk

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: <1301064627.2250.215.camel@laptop>
Date:	Fri, 25 Mar 2011 15:50:27 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Ming Lei <tom.leiming@...il.com>
Cc:	torvalds@...l.org, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: deadlock caused by printk

On Fri, 2011-03-25 at 22:30 +0800, Ming Lei wrote:
> 
> But seems ftrace can't dump out the messages if system hangs,

True.

>  so could
> we introduce a smart and simple "printk" which can be used in any
> contexts? 

I think you could use early_printk() for that, it doesn't bother with
all the syslog muck.

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