On 2018/07/11 1:51, David Laight wrote: > From: Josh Poimboeuf >> Sent: 09 July 2018 20:12 >> On Mon, Jul 09, 2018 at 10:49:53AM +0200, Peter Zijlstra wrote: >>> On Sat, Jul 07, 2018 at 10:54:28PM +0900, Tetsuo Handa wrote: >>>>>> Since syzbot is confused by concurrent printk() messages [1], >>>>>> this patch changes show_opcodes() to use snprintf(). >>> >>> But how big of a problem is that really? We can't very well remove all >>> pr_cont stuff from the kernel. >> >> I'd say we should try to make oopses as legible as possible. > > To make oopses legible you need to lock the output between output lines. > Which would require a 'KERN_CONTINUED' marker on the previous print.
There is an attempt to prefix context identifier to each line of output ( https://groups.google.com/d/msg/syzkaller/ttZehjXiHTU/JR67pXz3BAAJ ). Therefore, I expect oops messages can stop using pr_cont()/KERN_CONT.
