INFO: task syz-executor can't die for more than 146 seconds.

0 views
Skip to first unread message

syzbot

unread,
Nov 19, 2019, 1:55:08 AM11/19/19
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 5a6fcbea Add linux-next specific files for 20191115
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=146b9836e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8eac90e6ae4ab399
dashboard link: https://syzkaller.appspot.com/bug?extid=44cfaf58aaca84e1681b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [fred...@kernel.org gre...@linuxfoundation.org
linux-...@vger.kernel.org mi...@kernel.org npi...@gmail.com
pet...@infradead.org tg...@linutronix.de]

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+44cfaf...@syzkaller.appspotmail.com

INFO: task syz-executor.0:8928 can't die for more than 146 seconds.
syz-executor.0 R running task 28144 8928 8884 0x00004004
Call Trace:
context_switch kernel/sched/core.c:3385 [inline]
__schedule+0x8e1/0x1f30 kernel/sched/core.c:4081
retint_kernel+0x1b/0x2b
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:136 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:166 [inline]
RIP: 0010:check_memory_region_inline mm/kasan/generic.c:182 [inline]
RIP: 0010:check_memory_region+0x4f/0x1a0 mm/kasan/generic.c:192
Code: 01 00 00 4c 8d 5c 37 ff 49 89 f8 48 b8 00 00 00 00 00 fc ff df 4d 89
da 49 c1 e8 03 4d 8d 24 00 49 c1 ea 03 49 01 c2 4c 89 e0 <49> 8d 5a 01 49
89 d9 4d 29 e1 49 83 f9 10 0f 8e ad 00 00 00 45 89
RSP: 0018:ffff88805ed3fbd0 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff13
RAX: ffff88805ed3fc28 RBX: ffffffff87600a20 RCX: 0000000000000002
RDX: ffff888095d8e40b RSI: ffffed1012bb1c81 RDI: ffffed1012bb1c82
RBP: ffff88805ed3fb59 R08: ffff888095d8e408 R09: 0000000000000003
R10: ffffed1012bb1c81 R11: ffff88805ed3fcc8 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
INFO: task syz-executor.1:8929 can't die for more than 151 seconds.
syz-executor.1 R running task 28144 8929 8886 0x00004004
Call Trace:
context_switch kernel/sched/core.c:3385 [inline]
__schedule+0x8e1/0x1f30 kernel/sched/core.c:4081
preempt_schedule_irq+0xb5/0x160 kernel/sched/core.c:4338
retint_kernel+0x1b/0x2b
RIP: 0010:atomic_read include/asm-generic/atomic-instrumented.h:26 [inline]
RIP: 0010:irq_work_sync+0xd3/0x1d0 kernel/irq_work.c:193
Code: f5 ff 4d 89 e6 4d 89 e5 48 b8 00 00 00 00 00 fc ff df 49 c1 ee 03 41
83 e5 07 49 01 c6 41 83 c5 03 eb 07 e8 7f 87 f5 ff f3 90 <e8> 78 87 f5 ff
be 04 00 00 00 4c 89 e7 e8 ab a6 31 00 41 0f b6 06
RSP: 0018:ffff88805eda7c08 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13
RAX: ffff88805ed9e180 RBX: 0000000000000002 RCX: ffffffff817e51f6
RDX: 0000000000000000 RSI: ffffffff817e51c1 RDI: 0000000000000005
RBP: ffff88805eda7c28 R08: ffff88805ed9e180 R09: ffffed1012cab282
R10: ffffed1012cab281 R11: ffff88809655940b R12: ffff888096559408
R13: ffff88805eda7bf8 R14: ffff888096559408 R15: 0000000000000003


---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Nov 19, 2019, 5:03:47 AM11/19/19
to Tetsuo Handa, penguin...@i-love.sakura.ne.jp, syzkaller-upst...@googlegroups.com
> irq_work_sync

> #syz dup: INFO: task syz-executor can't die for more than 143 seconds. (2)

Your 'dup:' command is accepted, but please keep
syzkaller-upst...@googlegroups.com mailing list in CC next
time. It serves as a history of what happened with each bug report. Thank
you.


Reply all
Reply to author
Forward
0 new messages