[Android 5.15] BUG: scheduling while atomic in do_task_dead
0 views
Skip to first unread message
syzbot
Feb 15, 2024, 10:18:30 PMFeb 15
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 993bed180178 Merge "Merge branch 'android13-5.15' into bra..
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=17f81a10180000
kernel config: https://syzkaller.appspot.com/x/.config?x=49ce29477ba81e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=4326448875ec2cca0050
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11258494180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=139f6398180000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/803c31a2cd6a/disk-993bed18.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fb3ff89c92a4/vmlinux-993bed18.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b0859874279b/bzImage-993bed18.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+432644...@syzkaller.appspotmail.com
BUG: scheduling while atomic: syz-executor175/381/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8165ea9a>] is_module_text_address+0x1a/0x140 kernel/module.c:4811
CPU: 0 PID: 381 Comm: syz-executor175 Not tainted 5.15.148-syzkaller-00718-g993bed180178 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x17 lib/dump_stack.c:113
__schedule_bug+0x195/0x260 kernel/sched/core.c:5707
schedule_debug kernel/sched/core.c:5734 [inline]
__schedule+0xd19/0x1590 kernel/sched/core.c:6402
do_task_dead+0x99/0xa0 kernel/sched/core.c:6530
do_exit+0x2089/0x2ca0 kernel/exit.c:929
do_group_exit+0x141/0x310 kernel/exit.c:1000
__do_sys_exit_group kernel/exit.c:1011 [inline]
__se_sys_exit_group kernel/exit.c:1009 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1009
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fcff6ce6039
Code: Unable to access opcode bytes at RIP 0x7fcff6ce600f.
RSP: 002b:00007fff7d54d808 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcff6ce6039
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007fcff6d622b0 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fcff6d622b0
R13: 0000000000000000 R14: 00007fcff6d62d20 R15: 00007fcff6cb71c0
</TASK>
---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: 993bed180178 Merge "Merge branch 'android13-5.15' into bra..
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=17f81a10180000
kernel config: https://syzkaller.appspot.com/x/.config?x=49ce29477ba81e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=4326448875ec2cca0050
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11258494180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=139f6398180000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/803c31a2cd6a/disk-993bed18.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fb3ff89c92a4/vmlinux-993bed18.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b0859874279b/bzImage-993bed18.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+432644...@syzkaller.appspotmail.com
BUG: scheduling while atomic: syz-executor175/381/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8165ea9a>] is_module_text_address+0x1a/0x140 kernel/module.c:4811
CPU: 0 PID: 381 Comm: syz-executor175 Not tainted 5.15.148-syzkaller-00718-g993bed180178 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x17 lib/dump_stack.c:113
__schedule_bug+0x195/0x260 kernel/sched/core.c:5707
schedule_debug kernel/sched/core.c:5734 [inline]
__schedule+0xd19/0x1590 kernel/sched/core.c:6402
do_task_dead+0x99/0xa0 kernel/sched/core.c:6530
do_exit+0x2089/0x2ca0 kernel/exit.c:929
do_group_exit+0x141/0x310 kernel/exit.c:1000
__do_sys_exit_group kernel/exit.c:1011 [inline]
__se_sys_exit_group kernel/exit.c:1009 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1009
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fcff6ce6039
Code: Unable to access opcode bytes at RIP 0x7fcff6ce600f.
RSP: 002b:00007fff7d54d808 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcff6ce6039
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007fcff6d622b0 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fcff6d622b0
R13: 0000000000000000 R14: 00007fcff6d62d20 R15: 00007fcff6cb71c0
</TASK>
---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Feb 18, 2024, 11:42:23 AMFeb 18
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 92432f07d663 ANDROID: GKI: Update the ABI symbol list
syzbot found the following issue on:
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=14c5c872180000
kernel config: https://syzkaller.appspot.com/x/.config?x=54c503ca94c7e582
dashboard link: https://syzkaller.appspot.com/bug?extid=7b1188a51a265df3b1c1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1343f694180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=119effc8180000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1198f4a39d5a/disk-92432f07.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bbb166188387/vmlinux-92432f07.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2c2a856cab86/bzImage-92432f07.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
BUG: scheduling while atomic: syz-executor323/308/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8163d99f>] is_module_text_address+0x1f/0x360 kernel/module/main.c:3140
Preemption disabled at:
CPU: 1 PID: 308 Comm: syz-executor323 Not tainted 6.1.68-syzkaller-00023-g92432f07d663 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x1b lib/dump_stack.c:113
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
__schedule_bug+0x195/0x260 kernel/sched/core.c:5960
schedule_debug kernel/sched/core.c:5987 [inline]
__schedule+0xce9/0x1540 kernel/sched/core.c:6622
do_task_dead+0x99/0xa0 kernel/sched/core.c:6747
do_exit+0x202a/0x2b80 kernel/exit.c:927
do_group_exit+0x21a/0x2d0 kernel/exit.c:1025
get_signal+0x169d/0x1820 kernel/signal.c:2879
arch_do_signal_or_restart+0xb0/0x16f0 arch/x86/kernel/signal.c:871
exit_to_user_mode_loop+0x74/0xa0 kernel/entry/common.c:168
exit_to_user_mode_prepare+0x5a/0xa0 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x26/0x140 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ff77fa3d8d9
Code: Unable to access opcode bytes at 0x7ff77fa3d8af.
RSP: 002b:00007ff77f9fe228 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 00007ff77fac8328 RCX: 00007ff77fa3d8d9
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007ff77fac832c
RBP: 00007ff77fac8320 R08: 00007ff77f9fe6c0 R09: 00007ff77f9fe6c0
R10: 00007ff77f9fe6c0 R11: 0000000000000246 R12: 00007ff77fa94f6c
R13: 00007ff77fa94068 R14: 0000000020001940 R15: 00007ffde8ba0428
Reply all
Reply to author
Forward
0 new messages