[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180709173546.dc720ad918e5362b8be2e034@linux-foundation.org>
Date: Mon, 9 Jul 2018 17:35:46 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc: Dmitry Vyukov <dvyukov@...gle.com>,
Guenter Roeck <groeck@...gle.com>,
"Theodore Ts'o" <tytso@....edu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
syzkaller <syzkaller@...glegroups.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
David Miller <davem@...emloft.net>,
kbuild test robot <fengguang.wu@...el.com>
Subject: Re: what trees/branches to test on syzbot
On Sat, 7 Jul 2018 08:26:32 +0900 Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp> wrote:
> Hello Andrew,
>
> It seems that syzbot (experimentally ?) restarted testing linux-next.
>
> May I ask you to carry temporarily debug printk() patch at
> https://groups.google.com/d/msg/syzkaller-bugs/E8M8WTqt034/OpadOICfCAAJ
> for "INFO: task hung in __sb_start_write" case?
>
> The bug should be reproduced within a day if executed under syzbot environment.
> Thus, I'm sure that we don't need to carry this patch for long.
Sure, I can add that. Let's get the build warning sorted out first,
please. Any old silly workaround will suffice in a developer-only
debug patch.
Powered by blists - more mailing lists