From: Dmitry Vyukov <dvyukov@google.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: [PATCH] printk: Add caller information to printk() output.
Date: Thu, 3 Jan 2019 19:27:41 +0100 [thread overview]
Message-ID: <CACT4Y+ZKR7eib+ZtK-7mbCw6rD6KOeuWtjWtxAcnHEWnYqyjJw@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+ahbDb7F2B1-z5QxroZcqP+AEUfUi6Sa1ZHRpaCeVmZ=w@mail.gmail.com>
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.
next prev parent reply other threads:[~2019-01-03 18:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 7:37 [PATCH] printk: Add caller information to printk() output Tetsuo Handa
2018-11-30 15:40 ` Petr Mladek
2018-12-01 14:44 ` Tetsuo Handa
2018-12-02 11:23 ` Tetsuo Handa
2018-12-04 2:02 ` Sergey Senozhatsky
2018-12-04 10:16 ` Tetsuo Handa
2018-12-04 10:38 ` Sergey Senozhatsky
2018-12-04 15:31 ` Petr Mladek
2018-12-03 15:06 ` Petr Mladek
2018-12-03 21:10 ` Tetsuo Handa
2018-12-04 15:27 ` Petr Mladek
2018-12-05 10:42 ` Tetsuo Handa
2018-12-05 11:50 ` Sergey Senozhatsky
2018-12-07 4:58 ` Tetsuo Handa
2018-12-07 5:31 ` Sergey Senozhatsky
2018-12-10 13:09 ` Petr Mladek
2018-12-10 14:01 ` Tetsuo Handa
2018-12-11 10:26 ` Tetsuo Handa
2018-12-12 2:25 ` Sergey Senozhatsky
2018-12-12 2:29 ` Sergey Senozhatsky
2018-12-13 12:18 ` Petr Mladek
2018-12-13 12:42 ` Sergey Senozhatsky
2018-12-17 14:54 ` Petr Mladek
2018-12-17 15:40 ` Sergey Senozhatsky
2018-12-17 21:05 ` Tetsuo Handa
2018-12-18 8:39 ` Petr Mladek
2018-12-18 8:58 ` Sergey Senozhatsky
2019-01-02 16:09 ` Dmitry Vyukov
2019-01-03 18:27 ` Dmitry Vyukov [this message]
2019-01-04 7:33 ` Fengguang Wu
2019-01-11 19:34 ` Kevin Hilman
2019-01-10 11:27 ` Tetsuo Handa
2018-12-18 8:55 ` Sergey Senozhatsky
2018-12-18 10:01 ` Petr Mladek
2018-12-18 10:10 ` Sergey Senozhatsky
2019-03-21 2:59 ` Michael Ellerman
2019-03-21 10:20 ` Petr Mladek
2019-03-22 0:48 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACT4Y+ZKR7eib+ZtK-7mbCw6rD6KOeuWtjWtxAcnHEWnYqyjJw@mail.gmail.com \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=syzkaller@googlegroups.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).