On Fri, 20 Jul 2012 17:27:37 -0700
Anton Vorontsov <[email protected]> wrote:

> dmesg command appears to be broken after the printk rework. The old logic
> in kdb code makes no sense in terms of current printk/logging storage
> format, and KDB simply hangs forever.
> 
> This patch revives the command by switching to kmsg_dumper iterator.
> 
> The code is now much more simpler and shorter.
> 
> Signed-off-by: Anton Vorontsov <[email protected]>

This one should me merged into 3.5.1 methinks.  Note that it has been
merged into mainline without a -stable tag.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Reply via email to