[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190318140937.GA29374@tigerII.localdomain>
Date: Mon, 18 Mar 2019 23:09:37 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: [syzbot? printk?] no WARN_ON() messages printed before "Kernel
panic - not syncing: panic_on_warn set ..."
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.
-ss
Powered by blists - more mailing lists