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: <AANLkTimw1+6DrYxxzkw7yh-t4W8rM55qcVd1nsQrAYT-@mail.gmail.com>
Date:	Fri, 25 Mar 2011 22:30:29 +0800
From:	Ming Lei <tom.leiming@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	torvalds@...l.org, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: deadlock caused by printk

Hi,

2011/3/25 Peter Zijlstra <peterz@...radead.org>:
>> One thing you could to is use trace_printk() and use ftrace to debug
>> perf.
>
> That should still work.

I will try it, thanks.

But seems ftrace can't dump out the messages if system hangs, so could
we introduce a smart and simple "printk" which can be used in any
contexts?

thanks,
-- 
Lei Ming
--
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/