From: Dmitry Vyukov <dvyukov@google.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: [syzbot? printk?] no WARN_ON() messages printed before "Kernel panic - not syncing: panic_on_warn set ..."
Date: Tue, 19 Mar 2019 09:10:25 +0100 [thread overview]
Message-ID: <CACT4Y+Z_+H09iOPzSzJfs=_D=dczk22gL02FjuZ6HXO+p0kRyA@mail.gmail.com> (raw)
In-Reply-To: <20190318140937.GA29374@tigerII.localdomain>
On Mon, Mar 18, 2019 at 3:09 PM Sergey Senozhatsky
<sergey.senozhatsky@gmail.com> wrote:
>
> On (03/18/19 14:42), Dmitry Vyukov wrote:
> > > There is also SYSLOG_ACTION_CONSOLE_OFF, which disables logging.
> >
> > That one I somehow figured earlier, here is the exact check:
> > https://github.com/google/syzkaller/blob/61f9c92f3a465025d2b9d91f429aaec968aeaa2a/sys/linux/init.go#L152-L155
>
> OK, cool.
> You probably would also want to add SYSLOG_ACTION_CLEAR to the list.
It's not hard to add, but I would like to understand why exactly.
syzkaller reads out console output from qemu, GCE VM, android phone
all the time. So if something was already written and we read it out
right away, it seems that clearing won't affect things. Does
SYSLOG_ACTION_CLEAR affect only reading output via syslog syscall,
/dev/something?
In some setups we read out output with "dmesg -w" (should stream
output as well) in absence of a better solution. Will this be affected
by SYSLOG_ACTION_CLEAR?
next prev parent reply other threads:[~2019-03-19 8:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 2:09 [syzbot? printk?] no WARN_ON() messages printed before "Kernel panic - not syncing: panic_on_warn set ..." Tetsuo Handa
2019-03-16 9:11 ` Dmitry Vyukov
2019-03-16 10:18 ` Tetsuo Handa
2019-03-16 14:14 ` Sergey Senozhatsky
2019-03-16 14:16 ` Dmitry Vyukov
2019-03-16 14:40 ` Sergey Senozhatsky
2019-03-16 14:53 ` Tetsuo Handa
2019-03-16 14:57 ` Dmitry Vyukov
2019-03-16 15:02 ` Tetsuo Handa
2019-03-16 15:10 ` Dmitry Vyukov
2019-03-18 5:27 ` Tetsuo Handa
2019-03-18 12:07 ` Dmitry Vyukov
2019-03-18 12:32 ` Dmitry Vyukov
2019-03-18 12:39 ` Dmitry Vyukov
2019-03-19 0:41 ` Tetsuo Handa
2019-03-18 12:50 ` Sergey Senozhatsky
2019-03-18 13:42 ` Dmitry Vyukov
2019-03-18 14:09 ` Sergey Senozhatsky
2019-03-19 8:10 ` Dmitry Vyukov [this message]
2019-03-19 12:35 ` Sergey Senozhatsky
2019-03-19 13:35 ` Dmitry Vyukov
2019-05-08 10:31 ` Tetsuo Handa
2019-05-09 9:58 ` Sergey Senozhatsky
2019-05-09 10:18 ` Sergey Senozhatsky
2019-05-09 10:40 ` Tetsuo Handa
2019-05-09 10:26 ` Tetsuo Handa
2019-05-09 10:36 ` Sergey Senozhatsky
2019-05-10 14:12 ` Petr Mladek
2019-05-10 14:53 ` 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+Z_+H09iOPzSzJfs=_D=dczk22gL02FjuZ6HXO+p0kRyA@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=syzkaller@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.