lkml.org 
[lkml]   [2018]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: INFO: task hung in fsnotify_connector_destroy_workfn (2)
From
Date
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().

\
 
 \ /
  Last update: 2018-09-15 19:26    [W:0.087 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site