From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot <syzbot+6fb572170402d311dd39@syzkaller.appspotmail.com>,
amir73il@gmail.com, jack@suse.cz,
syzkaller-bugs@googlegroups.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: INFO: task hung in fsnotify_connector_destroy_workfn (2)
Date: Sun, 16 Sep 2018 02:25:53 +0900 [thread overview]
Message-ID: <2f4ce251-cf84-8bd2-72fc-a3ff687d5188@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <0000000000006364200575dfc280@google.com>
On 2018/09/15 11:33, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 11da3a7f84f1 Linux 4.19-rc3
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=141ffbca400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=9917ff4b798e1a1e
> dashboard link: https://syzkaller.appspot.com/bug?extid=6fb572170402d311dd39
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=136a60ae400000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+6fb572170402d311dd39@syzkaller.appspotmail.com
>
Since it kept printk()ing for at least 93 seconds, it might have kept for 150 seconds.
[ 174.614333] hid-generic 0000:0000:0000.0003: unknown main item tag 0x0
[ 268.196102] INFO: task kworker/u4:1:23 blocked for more than 140 seconds.
Since the reproducer is simple, this might be lockup due to continuous printk().
If syzbot can reliably reproduce this problem using the reproducer, try
ratelimiting printk().
next prev parent reply other threads:[~2018-09-15 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 2:33 INFO: task hung in fsnotify_connector_destroy_workfn (2) syzbot
2018-09-15 16:42 ` Amir Goldstein
2018-09-15 17:25 ` Tetsuo Handa [this message]
2018-09-15 23:05 ` Amir Goldstein
2018-09-24 13:19 ` Jiri Kosina
2018-09-24 13:31 ` Dmitry Vyukov
2018-09-24 14:03 ` Tetsuo Handa
2018-09-25 8:55 ` Petr Mladek
2018-09-25 12:30 ` Tetsuo Handa
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=2f4ce251-cf84-8bd2-72fc-a3ff687d5188@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+6fb572170402d311dd39@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).