LKML Archive on
help / color / mirror / Atom feed
From: Tetsuo Handa <>
To: Sergey Senozhatsky <>
Cc: Andrew Morton <>,, Dmitry Vyukov <>,
	Petr Mladek <>,
	Steven Rostedt <>
Subject: Re: [PATCH] printk: Monitor change of console loglevel.
Date: Wed, 15 May 2019 23:32:24 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20190514091917.GA26804@jagdpanzerIV>

On 2019/05/14 18:19, Sergey Senozhatsky wrote:
> On (05/11/19 00:19), Tetsuo Handa wrote:
>> We are seeing syzbot reports [1] where printk() messages prior to panic()
>> are missing for unknown reason. To test whether it is due to some testcase
>> changing console loglevel, let's panic() as soon as console loglevel has
>> changed. This patch is intended for testing on linux-next.git only, and
>> will be removed after we found what is wrong.
> Clone linux-next, apply the patch, push to a github/gitlab repo,
> configure syzbot to pull from github/gitlab?

I think that it is practically impossible to do so from the point of
view of automation.

>                                              Adding temp patches
> to linux-next is hard and apparently not exactly what linux-next
> is used for these days.

Currently Andrew Morton is carrying "linux-next.git only" patches
(a.k.a. CONFIG_DEBUG_AID_FOR_SYZBOT patches) via mmotm tree.

It would be nice if linux-next.git can directly import temp patches
using "quilt push -a" on patches from a subversion repository. Then,
we can casually add/remove/update temp patches like this.

  reply	other threads:[~2019-05-15 14:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 15:19 Tetsuo Handa
2019-05-14  9:19 ` Sergey Senozhatsky
2019-05-15 14:32   ` Tetsuo Handa [this message]
2019-05-23  9:56     ` Tetsuo Handa
2019-05-24  7:55       ` Dmitry Vyukov
2019-05-24 10:35         ` Tetsuo Handa
2019-05-24 17:17 ` Linus Torvalds
2019-05-24 17:40   ` Joe Perches
2019-05-24 17:55     ` Linus Torvalds
2019-05-25  0:14   ` Tetsuo Handa
2019-05-25  0:56     ` Joe Perches

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] printk: Monitor change of console loglevel.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).