lkml.org 
[lkml]   [2019]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] printk: Monitor change of console loglevel.
From
Date
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.

\
 
 \ /
  Last update: 2019-05-15 16:35    [W:0.053 / U:23.828 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site