From: Dmitry Vyukov <dvyukov@google.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kconfig: Add kernel config option for fuzz testing.
Date: Tue, 17 Dec 2019 09:38:41 +0100 [thread overview]
Message-ID: <CACT4Y+bdvwSBTeqkfJ3kWMOB_QSq84TzumeoTzv89v3in-439A@mail.gmail.com> (raw)
In-Reply-To: <20191217082449.GC54407@google.com>
On Tue, Dec 17, 2019 at 9:24 AM Sergey Senozhatsky
<sergey.senozhatsky.work@gmail.com> wrote:
>
> On (19/12/17 08:54), Dmitry Vyukov wrote:
> > On Tue, Dec 17, 2019 at 6:12 AM Sergey Senozhatsky
> > <sergey.senozhatsky.work@gmail.com> wrote:
> > >
> > > On (19/12/16 18:59), Tetsuo Handa wrote:
> > >
> > > Can you fuzz test with `ignore_loglevel'?
> >
> > We can set ignore_loglevel in syzbot configs, but won't it then print
> > everything including verbose debug output?
>
> What would be the most active source of debug output?
>
> dev_dbg(), which is dev_printk(KERN_DEBUG), can be compiled out, if I'm
> not mistaken. It probably depends on CONFIG_DEBUG or something similar,
> unlike dev_printk(), which depends on CONFIG_PRINTK. It seems that we have
> significantly more dev_dbg() users, than direct dev_printk(KERN_DEBUG).
>
> Does fuzz tester hit pr_debug() often? File systems? Some of them
> have ways to compile out debugging output as well. E.g. jbd_debug,
> _debug, ext4_debug, and so on.
As far as I remember it produces an infinite amount of output on debug
level. Even for normal level it produces much more than one would
normally expect as it does random things all over the kernel with
maximum frequency.
next prev parent reply other threads:[~2019-12-17 8:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 9:59 [PATCH] kconfig: Add kernel config option for fuzz testing Tetsuo Handa
2019-12-16 11:46 ` Greg Kroah-Hartman
2019-12-16 15:35 ` Tetsuo Handa
2019-12-16 16:31 ` Greg Kroah-Hartman
2019-12-16 20:18 ` Theodore Y. Ts'o
2019-12-16 21:06 ` Tetsuo Handa
2019-12-17 8:36 ` Dmitry Vyukov
2019-12-17 8:53 ` Dmitry Vyukov
2020-01-02 19:57 ` Matthew Garrett
2020-02-18 10:54 ` Tetsuo Handa
2020-02-27 22:10 ` Tetsuo Handa
2020-02-27 22:15 ` Matthew Garrett
2019-12-17 15:52 ` Theodore Y. Ts'o
2019-12-19 17:43 ` Dmitry Vyukov
2019-12-19 21:18 ` Theodore Y. Ts'o
2019-12-18 10:29 ` Tetsuo Handa
2019-12-19 17:21 ` Dmitry Vyukov
2019-12-16 18:34 ` Andi Kleen
2019-12-16 18:47 ` Greg Kroah-Hartman
2019-12-17 5:12 ` Sergey Senozhatsky
2019-12-17 7:54 ` Dmitry Vyukov
2019-12-17 8:24 ` Sergey Senozhatsky
2019-12-17 8:38 ` Dmitry Vyukov [this message]
2019-12-17 5:42 ` Masahiro Yamada
2019-12-17 8:41 ` Dmitry Vyukov
2019-12-17 12:54 ` Tetsuo Handa
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+bdvwSBTeqkfJ3kWMOB_QSq84TzumeoTzv89v3in-439A@mail.gmail.com \
--to=dvyukov@google.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.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=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).