On Mon, Jul 23, 2012 at 04:19:27PM -0700, Andrew Morton 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.
Thanks to Linus, it made it into v3.5 release, so I believe there is no need for -stable. Cheers, -- Anton Vorontsov Email: [email protected] ------------------------------------------------------------------------------ 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
