WARNING in enqueue_task_dl
18 views
Skip to first unread message
syzbot
Jul 20, 2019, 1:35:07 AM7/20/19
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 3bd837bf Linux 4.19.59
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14f07900600000
kernel config: https://syzkaller.appspot.com/x/.config?x=cfa2f3bc2e9ff5d4
dashboard link: https://syzkaller.appspot.com/bug?extid=5dc1b5289479c434cd72
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1287b634600000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+5dc1b5...@syzkaller.appspotmail.com
8021q: adding VLAN 0 to HW filter on device batadv0
audit: type=1400 audit(1563597104.508:38): avc: denied { associate } for
pid=7611 comm="syz-executor.0" name="syz0"
scontext=unconfined_u:object_r:unlabeled_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1
WARNING: CPU: 1 PID: 7620 at kernel/sched/deadline.c:627
rt_mutex_get_top_task /./include/linux/sched/rt.h:38 [inline]
WARNING: CPU: 1 PID: 7620 at kernel/sched/deadline.c:627
enqueue_task_dl+0x1c53/0x2d70 /kernel/sched/deadline.c:1441
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 7620 Comm: syz-executor.0 Not tainted 4.19.59 #32
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+0x172/0x1f0 /lib/dump_stack.c:113
panic+0x263/0x507 /kernel/panic.c:185
__warn.cold+0x20/0x4a /kernel/panic.c:540
report_bug+0x263/0x2b0 /lib/bug.c:186
fixup_bug /arch/x86/kernel/traps.c:178 [inline]
fixup_bug /arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x204/0x360 /arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 /arch/x86/kernel/traps.c:316
invalid_op+0x14/0x20 /arch/x86/entry/entry_64.S:1013
RIP: 0010:setup_new_dl_entity /kernel/sched/deadline.c:627 [inline]
RIP: 0010:enqueue_dl_entity /kernel/sched/deadline.c:1428 [inline]
RIP: 0010:enqueue_task_dl+0x1c53/0x2d70 /kernel/sched/deadline.c:1499
Code: 37 00 48 c1 ea 03 48 c1 e0 2a 80 3c 02 00 0f 85 bc 0a 00 00 49 8b 85
50 0a 00 00 e9 e1 f5 ff ff e8 82 eb 51 00 e9 e9 e3 ff ff <0f> 0b e9 23 f5
ff ff 0f 0b e9 88 f5 ff ff 4c 89 4d b0 4c 89 45 b8
RSP: 0018:ffff88809fb47c90 EFLAGS: 00010002
RAX: 0000000000000000 RBX: ffffffff88b09b00 RCX: 0000000000000002
RDX: 0000000c78d28814 RSI: 1ffffffff10965dd RDI: ffffffff884b2ee8
RBP: ffff88809fb47d08 R08: ffff88807f20e2f8 R09: ffff88807f20e340
R10: ffff88807f20e0bc R11: ffff8880ae923993 R12: ffff88807f20e080
R13: ffff8880ae92d240 R14: ffff8880ae92d240 R15: ffff88807f20e34c
enqueue_task+0xa0/0x1d0 /kernel/sched/core.c:728
__sched_setscheduler+0xd35/0x1d90 /kernel/sched/core.c:4338
sched_setattr /kernel/sched/core.c:4396 [inline]
__do_sys_sched_setattr /kernel/sched/core.c:4572 [inline]
__se_sys_sched_setattr /kernel/sched/core.c:4551 [inline]
__x64_sys_sched_setattr+0x184/0x2b0 /kernel/sched/core.c:4551
do_syscall_64+0xfd/0x620 /arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x459819
Code: fd b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 cb b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f125bf71c78 EFLAGS: 00000246 ORIG_RAX: 000000000000013a
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000459819
RDX: 0000000000000000 RSI: 0000000020000000 RDI: 0000000000000000
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f125bf726d4
R13: 00000000004c6d52 R14: 00000000004dc010 R15: 00000000ffffffff
======================================================
---
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 can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
syzbot found the following crash on:
HEAD commit: 3bd837bf Linux 4.19.59
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14f07900600000
kernel config: https://syzkaller.appspot.com/x/.config?x=cfa2f3bc2e9ff5d4
dashboard link: https://syzkaller.appspot.com/bug?extid=5dc1b5289479c434cd72
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1287b634600000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+5dc1b5...@syzkaller.appspotmail.com
8021q: adding VLAN 0 to HW filter on device batadv0
audit: type=1400 audit(1563597104.508:38): avc: denied { associate } for
pid=7611 comm="syz-executor.0" name="syz0"
scontext=unconfined_u:object_r:unlabeled_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1
WARNING: CPU: 1 PID: 7620 at kernel/sched/deadline.c:627
rt_mutex_get_top_task /./include/linux/sched/rt.h:38 [inline]
WARNING: CPU: 1 PID: 7620 at kernel/sched/deadline.c:627
enqueue_task_dl+0x1c53/0x2d70 /kernel/sched/deadline.c:1441
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 7620 Comm: syz-executor.0 Not tainted 4.19.59 #32
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+0x172/0x1f0 /lib/dump_stack.c:113
panic+0x263/0x507 /kernel/panic.c:185
__warn.cold+0x20/0x4a /kernel/panic.c:540
report_bug+0x263/0x2b0 /lib/bug.c:186
fixup_bug /arch/x86/kernel/traps.c:178 [inline]
fixup_bug /arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x204/0x360 /arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 /arch/x86/kernel/traps.c:316
invalid_op+0x14/0x20 /arch/x86/entry/entry_64.S:1013
RIP: 0010:setup_new_dl_entity /kernel/sched/deadline.c:627 [inline]
RIP: 0010:enqueue_dl_entity /kernel/sched/deadline.c:1428 [inline]
RIP: 0010:enqueue_task_dl+0x1c53/0x2d70 /kernel/sched/deadline.c:1499
Code: 37 00 48 c1 ea 03 48 c1 e0 2a 80 3c 02 00 0f 85 bc 0a 00 00 49 8b 85
50 0a 00 00 e9 e1 f5 ff ff e8 82 eb 51 00 e9 e9 e3 ff ff <0f> 0b e9 23 f5
ff ff 0f 0b e9 88 f5 ff ff 4c 89 4d b0 4c 89 45 b8
RSP: 0018:ffff88809fb47c90 EFLAGS: 00010002
RAX: 0000000000000000 RBX: ffffffff88b09b00 RCX: 0000000000000002
RDX: 0000000c78d28814 RSI: 1ffffffff10965dd RDI: ffffffff884b2ee8
RBP: ffff88809fb47d08 R08: ffff88807f20e2f8 R09: ffff88807f20e340
R10: ffff88807f20e0bc R11: ffff8880ae923993 R12: ffff88807f20e080
R13: ffff8880ae92d240 R14: ffff8880ae92d240 R15: ffff88807f20e34c
enqueue_task+0xa0/0x1d0 /kernel/sched/core.c:728
__sched_setscheduler+0xd35/0x1d90 /kernel/sched/core.c:4338
sched_setattr /kernel/sched/core.c:4396 [inline]
__do_sys_sched_setattr /kernel/sched/core.c:4572 [inline]
__se_sys_sched_setattr /kernel/sched/core.c:4551 [inline]
__x64_sys_sched_setattr+0x184/0x2b0 /kernel/sched/core.c:4551
do_syscall_64+0xfd/0x620 /arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x459819
Code: fd b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 cb b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f125bf71c78 EFLAGS: 00000246 ORIG_RAX: 000000000000013a
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000459819
RDX: 0000000000000000 RSI: 0000000020000000 RDI: 0000000000000000
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f125bf726d4
R13: 00000000004c6d52 R14: 00000000004dc010 R15: 00000000ffffffff
======================================================
---
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 can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
syzbot
Jul 20, 2019, 4:10:06 AM7/20/19
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: aea8526e Linux 4.14.133
syzbot found the following crash on:
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13c0b4f4600000
kernel config: https://syzkaller.appspot.com/x/.config?x=5dfccef5a159766b
dashboard link: https://syzkaller.appspot.com/bug?extid=5ac8bac25f95e8b221e7
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1550e1d0600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1272cc78600000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
audit: type=1400 audit(1563606392.882:36): avc: denied { map } for
pid=6969 comm="syz-executor366" path="/root/syz-executor366756543"
dev="sda1" ino=16483 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
IPVS: ftp: loaded support on port[0] = 21
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6973 at kernel/sched/deadline.c:593
setup_new_dl_entity /kernel/sched/deadline.c:594 [inline]
WARNING: CPU: 0 PID: 6973 at kernel/sched/deadline.c:593 enqueue_dl_entity
/kernel/sched/deadline.c:1370 [inline]
WARNING: CPU: 0 PID: 6973 at kernel/sched/deadline.c:593
enqueue_task_dl+0x1c17/0x2ba0 /kernel/sched/deadline.c:1441
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 6973 Comm: syz-executor366 Not tainted 4.14.133 #28
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack /lib/dump_stack.c:17 [inline]
Google 01/01/2011
Call Trace:
dump_stack+0x138/0x19c /lib/dump_stack.c:53
panic+0x1f2/0x426 /kernel/panic.c:182
__warn.cold+0x2f/0x36 /kernel/panic.c:546
report_bug+0x216/0x254 /lib/bug.c:186
fixup_bug /arch/x86/kernel/traps.c:177 [inline]
fixup_bug /arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x1bb/0x310 /arch/x86/kernel/traps.c:295
do_invalid_op+0x1b/0x20 /arch/x86/kernel/traps.c:314
invalid_op+0x1b/0x40 /arch/x86/entry/entry_64.S:960
RIP: 0010:setup_new_dl_entity /kernel/sched/deadline.c:593 [inline]
RIP: 0010:enqueue_dl_entity /kernel/sched/deadline.c:1370 [inline]
RIP: 0010:enqueue_task_dl+0x1c17/0x2ba0 /kernel/sched/deadline.c:1441
RSP: 0018:ffff888098a3fcd8 EFLAGS: 00010002
RAX: 0000000000000000 RBX: ffffffff87ab2780 RCX: 1ffff1101041413a
RDX: 0000000ad48fb497 RSI: ffff8880aee2c518 RDI: ffff8880820a09d0
RBP: ffff888098a3fd48 R08: ffff8880820a09cc R09: ffff8880820a09c0
R10: ffff8880820a073c R11: 0000000000000001 R12: ffff8880820a0700
R13: ffff8880aee2c500 R14: ffff8880820a0978 R15: ffff8880aee2c500
enqueue_task /kernel/sched/core.c:762 [inline]
__sched_setscheduler+0xd17/0x2510 /kernel/sched/core.c:4227
sched_setattr /kernel/sched/core.c:4285 [inline]
SYSC_sched_setattr /kernel/sched/core.c:4456 [inline]
SyS_sched_setattr+0x1f8/0x300 /kernel/sched/core.c:4435
do_syscall_64+0x1e8/0x640 /arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x446749
RSP: 002b:00007ff022092db8 EFLAGS: 00000246 ORIG_RAX: 000000000000013a
RAX: ffffffffffffffda RBX: 00000000006dbc38 RCX: 0000000000446749
RDX: 0000000000000000 RSI: 0000000020000000 RDI: 0000000000000000
RBP: 00000000006dbc30 R08: 00007ff022093700 R09: 0000000000000000
R10: 00007ff022093700 R11: 0000000000000246 R12: 00000000006dbc3c
R13: 00007ffdbf86bf7f R14: 00007ff0220939c0 R15: 0000000000000000
syzbot
Jul 13, 2020, 10:02:08 AM7/13/20
to syzkaller...@googlegroups.com
syzbot suspects this bug was fixed by commit:
commit edf55b5e3bde2fdba1a304b8e069154a4312f566
Author: Juri Lelli <juri....@redhat.com>
Date: Wed Jun 17 07:29:19 2020 +0000
sched/deadline: Initialize ->dl_boosted
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1720e5fb100000
start commit: 3bd837bf Linux 4.19.59
git tree: linux-4.19.y
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: sched/deadline: Initialize ->dl_boosted
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit edf55b5e3bde2fdba1a304b8e069154a4312f566
Author: Juri Lelli <juri....@redhat.com>
Date: Wed Jun 17 07:29:19 2020 +0000
sched/deadline: Initialize ->dl_boosted
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1720e5fb100000
start commit: 3bd837bf Linux 4.19.59
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=cfa2f3bc2e9ff5d4
dashboard link: https://syzkaller.appspot.com/bug?extid=5dc1b5289479c434cd72
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1287b634600000
dashboard link: https://syzkaller.appspot.com/bug?extid=5dc1b5289479c434cd72
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: sched/deadline: Initialize ->dl_boosted
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages