lkml.org 
[lkml]   [2019]   [Jan]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] printk: Add caller information to printk() output.
On Thu, Jan 03, 2019 at 07:27:41PM +0100, Dmitry Vyukov wrote:
>On Wed, Jan 2, 2019 at 5:09 PM Dmitry Vyukov <dvyukov@google.com> wrote:
>>
>> On Tue, Dec 18, 2018 at 9:58 AM Sergey Senozhatsky
>> <sergey.senozhatsky.work@gmail.com> wrote:
>> >
>> > On (12/18/18 09:39), Petr Mladek wrote:
>> > >
>> > > Sergey, are you okay with this squashed patch, please?
>> > >
>> >
>> > Yeah. There are several minor nitpicks, but here is my
>> > Acked-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
>> >
>> >
>> > One final question - can syzbot folks confirm that the patch
>> > helps? Just curious.
>>
>> This slip through the cracks. Tetsuo pinged me and I am testing now.
>> Need to create a set of tests and update parsing code to handle this.
>
>I've pushed support for CONFIG_PRINTK_CALLER to syzkaller/syzbot:
>https://github.com/google/syzkaller/commit/7da2392541a49c3f17b2e7d24e04b84d72b965fb
>Let's see what happens. Limited local testing shows that it's working
>as intended and significatly improves quality of reports and ability
>to make sense out of kernel output.
>
>Tetsuo, thanks for your great persistence with this change!
>Sergey, Petr, thanks for reviews!
>
>+Fengguang, Kevin, maybe you will find this useful for 0-day/kernel-ci.

Thanks! We'll try out CONFIG_PRINTK_CALLER.

Regards,
Fengguang

\
 
 \ /
  Last update: 2019-01-04 08:35    [W:0.109 / U:9.956 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site