From: Andrew Morton <akpm@linux-foundation.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Guenter Roeck <groeck@google.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
kbuild test robot <fengguang.wu@intel.com>
Subject: Re: what trees/branches to test on syzbot
Date: Mon, 9 Jul 2018 17:35:46 -0700 [thread overview]
Message-ID: <20180709173546.dc720ad918e5362b8be2e034@linux-foundation.org> (raw)
In-Reply-To: <e05a0804-6759-7579-c1d6-f0e80daf36ae@I-love.SAKURA.ne.jp>
On Sat, 7 Jul 2018 08:26:32 +0900 Tetsuo Handa <penguin-kernel@I-love.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.
next prev parent reply other threads:[~2018-07-10 0:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 7:51 Dmitry Vyukov
2018-01-16 9:45 ` Guenter Roeck
2018-01-16 9:58 ` Dmitry Vyukov
2018-01-16 16:58 ` Guenter Roeck
2018-01-16 17:02 ` Eric W. Biederman
2018-01-16 17:34 ` Greg Kroah-Hartman
2018-01-22 13:32 ` Dmitry Vyukov
2018-06-09 6:31 ` Tetsuo Handa
2018-06-09 22:17 ` Linus Torvalds
2018-06-10 1:51 ` Theodore Y. Ts'o
2018-06-10 6:11 ` Dmitry Vyukov
2018-06-11 1:22 ` Theodore Y. Ts'o
2018-06-15 9:54 ` Dmitry Vyukov
2018-06-18 4:52 ` Stephen Rothwell
2018-06-18 6:10 ` Eric W. Biederman
2018-06-18 13:54 ` Alan Cox
2018-06-26 10:54 ` Tetsuo Handa
2018-06-26 14:16 ` Theodore Y. Ts'o
2018-06-26 14:38 ` Dmitry Vyukov
2018-06-26 14:54 ` Guenter Roeck
2018-06-26 20:37 ` Tetsuo Handa
2018-07-05 10:49 ` Tetsuo Handa
2018-07-06 23:26 ` Tetsuo Handa
2018-07-10 0:35 ` Andrew Morton [this message]
2018-07-10 2:13 ` Tetsuo Handa
2018-01-19 1:48 ` Fengguang Wu
2018-01-22 13:34 ` Dmitry Vyukov
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=20180709173546.dc720ad918e5362b8be2e034@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sfr@canb.auug.org.au \
--cc=syzkaller@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome