corrupted report (2)

16 views
Skip to first unread message

syzbot

unread,
Apr 11, 2018, 5:52:01 AM4/11/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot hit the following crash on upstream commit
3fd14cdcc05a682b03743683ce3a726898b20555 (Fri Apr 6 19:15:41 2018 +0000)
Merge tag 'mtd/for-4.17' of git://git.infradead.org/linux-mtd
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=56275b6e83c2fb060948

So far this crash happened 8405 times on bpf-next,
https://github.com/google/kmsan.git/master, mmots, net-next, upstream.
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=5163486380294144
Kernel config:
https://syzkaller.appspot.com/x/.config?id=-5813481738265533882
compiler: gcc (GCC) 8.0.1 20180301 (experimental)
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org
penguin...@I-love.SAKURA.ne.jp vegard...@oracle.com]

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+56275b...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.

unregister_netdevice: waiting for lo to become free. Usage count = 2
unregister_netdevice: waiting for lo to become free. Usage count = 2
unregister_netdevice: waiting for lo to become free. Usage count = 2
unregister_netdevice: waiting for lo to become free. Usage count = 2
unregister_netdevice: waiting for lo to become free. Usage count = 2
Kernel panic - not syncing: hung_task: blocked tasks
CPU: 1 PID: 881 Comm: khungtaskd Not tainted 4.16.0+ #4
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1b9/0x294 lib/dump_stack.c:113
panic+0x22f/0x4de kernel/panic.c:183
check_hung_task kernel/hung_task.c:133 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:190 [inline]
watchdog+0xc21/0xf60 kernel/hung_task.c:249
kthread+0x345/0x410 kernel/kthread.c:238
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:411
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream

Dmitry Vyukov

unread,
May 7, 2019, 5:21:09 AM5/7/19
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation, Andrey Konovalov
From: syzbot <syzbot+56275b...@syzkaller.appspotmail.com>
Date: Wed, Apr 11, 2018 at 11:52 AM
To: <syzkaller-upst...@googlegroups.com>
Andrey,

We now have lots of crashes on usb fuzzer here with "[ 1306.165663][
T5528] usb 3-1: WARNING: ath10k USB support is incomplete, don't
expect anything to work!".
Please fix report parsing so that they are not detected as corrupted.
They are not corrupted.

Andrey Konovalov

unread,
May 8, 2019, 8:23:02 AM5/8/19
to Dmitry Vyukov, syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
I don't see them, where do I find them?

Dmitry Vyukov

unread,
May 8, 2019, 8:27:39 AM5/8/19
to Andrey Konovalov, syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
From: 'Andrey Konovalov' via syzkaller-upstream-moderation
<syzkaller-upst...@googlegroups.com>
Date: Wed, May 8, 2019 at 2:23 PM
To: Dmitry Vyukov
Cc: syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
The dashboard link above. See crashes on "ci2-upstream-usb" instance.
Reply all
Reply to author
Forward
0 new messages