On Fri, 2014-11-07 at 18:47 +0000, Daniel Thompson wrote: > Currently when kdb traps printk messages then the raw log level prefix > (consisting of '\001' followed by a numeral) does not get stripped off > before the message is issued to the various I/O handlers supported by > kdb. This causes annoying visual noise as well as causing problems > grepping for ^. It is also a change of behaviour compared to normal usage > of printk() usage. For example <SysRq>-h ends up with different output to > that of kdb's "sr h". > > This patch addresses the problem by stripping log levels from messages > before they are issued to the I/O handlers. printk() which can also > act as an i/o handler in some cases is special cased; if the caller > provided a log level then the prefix will be preserved when sent to > printk(). Andrew? Any thoughts on whether or not you are going to pick this up? -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html