[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+aFO+yZ7ovkxJOJfz=JgsE3yr+ywLQ9kVUrOHYMBgfWdg@mail.gmail.com>
Date: Fri, 18 May 2018 15:08:06 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Petr Mladek <pmladek@...e.com>
Cc: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
syzkaller <syzkaller@...glegroups.com>,
Steven Rostedt <rostedt@...dmis.org>,
Fengguang Wu <fengguang.wu@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] printk: inject caller information into the body of message
On Fri, May 18, 2018 at 2:54 PM, Petr Mladek <pmladek@...e.com> wrote:
> On Fri 2018-05-18 14:25:57, Dmitry Vyukov wrote:
>> > On Thu 2018-05-17 20:21:35, Sergey Senozhatsky wrote:
>> >> Dunno...
>> >> For instance, can we store context tracking info as a extended record
>> >> data? We have that dict/dict_len thing. So may we can store tracking
>> >> info there? Extended records will appear on the serial console /* if
>> >> console supports extended data */ or can be read in via devkmsg_read().
>>
>> What consoles do support it?
>> We are interested at least in qemu console, GCE console and Android
>> phone consoles. But it would be pity if this can't be used on various
>> development boards too.
>
> Only the netconsole is able to show the extended (dict)
> information at the moment. Search for CON_EXTENDED flag.
Then we won't be able to use it. And we can't pipe from devkmsg_read
in user-space, because we need this to work when kernel is broken in
various ways...
Powered by blists - more mailing lists