[Android 5.15] BUG: scheduling while atomic in do_nanosleep

0 views
Skip to first unread message

syzbot

unread,
Feb 5, 2024, 5:02:30 PMFeb 5
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3802b45594e1 Revert "clk: fixed-rate: add devm_clk_hw_regi..
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=13ee53c4180000
kernel config: https://syzkaller.appspot.com/x/.config?x=71b415a99493d134
dashboard link: https://syzkaller.appspot.com/bug?extid=056307f23e322d10c336
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=13444190180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f1713fe80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dd4d3bdb87f1/disk-3802b455.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a6dd15e230e4/vmlinux-3802b455.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ca3496f788a9/bzImage-3802b455.xz

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

BUG: scheduling while atomic: syz-executor957/294/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff84c6b408>] schedule+0x118/0x1e0 kernel/sched/core.c:6594
CPU: 1 PID: 294 Comm: syz-executor957 Not tainted 5.15.148-syzkaller-00704-g3802b45594e1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
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+0xd0b/0x1580 kernel/sched/core.c:6402
schedule+0x11f/0x1e0 kernel/sched/core.c:6595
freezable_schedule include/linux/freezer.h:197 [inline]
do_nanosleep+0x181/0x6a0 kernel/time/hrtimer.c:2044
hrtimer_nanosleep+0x1c5/0x3f0 kernel/time/hrtimer.c:2097
common_nsleep+0x91/0xb0 kernel/time/posix-timers.c:1267
__do_sys_clock_nanosleep kernel/time/posix-timers.c:1308 [inline]
__se_sys_clock_nanosleep+0x323/0x3b0 kernel/time/posix-timers.c:1285
__x64_sys_clock_nanosleep+0x9b/0xb0 kernel/time/posix-timers.c:1285
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:0x7f7a94ba34c3
Code: 00 00 00 00 00 66 90 83 ff 03 74 7b 83 ff 02 b8 fa ff ff ff 49 89 ca 0f 44 f8 80 3d be 1b 05 00 00 74 14 b8 e6 00 00 00 0f 05 <f7> d8 c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 28 48 89 54 24 10
RSP: 002b:00007ffecab73388 EFLAGS: 00000202 ORIG_RAX: 00000000000000e6
RAX: ffffffffffffffda RBX: 000000000000013d RCX: 00007f7a94ba34c3
RDX: 00007ffecab733a0 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00000000000f4240 R08: 00007ffecabca080 R09: 00007ffecabca0b0
R10: 0000000000000000 R11: 0000000000000202 R12: 000000000000632f
R13: 00007ffecab733dc R14: 00007ffecab733f0 R15: 00007ffecab733e0
</TASK>
BUG: scheduling while atomic: syz-executor957/294/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff84c6b408>] schedule+0x118/0x1e0 kernel/sched/core.c:6594
CPU: 1 PID: 294 Comm: syz-executor957 Tainted: G W 5.15.148-syzkaller-00704-g3802b45594e1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
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+0xd0b/0x1580 kernel/sched/core.c:6402
schedule+0x11f/0x1e0 kernel/sched/core.c:6595
freezable_schedule include/linux/freezer.h:197 [inline]
do_nanosleep+0x181/0x6a0 kernel/time/hrtimer.c:2044
hrtimer_nanosleep+0x1c5/0x3f0 kernel/time/hrtimer.c:2097
common_nsleep+0x91/0xb0 kernel/time/posix-timers.c:1267
__do_sys_clock_nanosleep kernel/time/posix-timers.c:1308 [inline]
__se_sys_clock_nanosleep+0x323/0x3b0 kernel/time/posix-timers.c:1285
__x64_sys_clock_nanosleep+0x9b/0xb0 kernel/time/posix-timers.c:1285
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:0x7f7a94ba34c3
Code: 00 00 00 00 00 66 90 83 ff 03 74 7b 83 ff 02 b8 fa ff ff ff 49 89 ca 0f 44 f8 80 3d be 1b 05 00 00 74 14 b8 e6 00 00 00 0f 05 <f7> d8 c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 28 48 89 54 24 10
RSP: 002b:00007ffecab73388 EFLAGS: 00000202 ORIG_RAX: 00000000000000e6
RAX: ffffffffffffffda RBX: 00000000000001ba RCX: 00007f7a94ba34c3
RDX: 00007ffecab733a0 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00000000000f4240 R08: 00007ffecabca080 R09: 00007ffecabca0b0
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000000070c9
R13: 00007ffecab733dc R14: 00007ffecab733f0 R15: 00007ffecab733e0
</TASK>
BUG: scheduling while atomic: syz-executor957/294/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff84c6b408>] schedule+0x118/0x1e0 kernel/sched/core.c:6594
CPU: 1 PID: 294 Comm: syz-executor957 Tainted: G W 5.15.148-syzkaller-00704-g3802b45594e1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
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+0xd0b/0x1580 kernel/sched/core.c:6402
schedule+0x11f/0x1e0 kernel/sched/core.c:6595
freezable_schedule include/linux/freezer.h:197 [inline]
do_nanosleep+0x181/0x6a0 kernel/time/hrtimer.c:2044
hrtimer_nanosleep+0x1c5/0x3f0 kernel/time/hrtimer.c:2097
common_nsleep+0x91/0xb0 kernel/time/posix-timers.c:1267
__do_sys_clock_nanosleep kernel/time/posix-timers.c:1308 [inline]
__se_sys_clock_nanosleep+0x323/0x3b0 kernel/time/posix-timers.c:1285
__x64_sys_clock_nanosleep+0x9b/0xb0 kernel/time/posix-timers.c:1285
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:0x7f7a94ba34c3
Code: 00 00 00 00 00 66 90 83 ff 03 74 7b 83 ff 02 b8 fa ff ff ff 49 89 ca 0f 44 f8 80 3d be 1b 05 00 00 74 14 b8 e6 00 00 00 0f 05 <f7> d8 c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 28 48 89 54 24 10
RSP: 002b:00007ffecab73388 EFLAGS: 00000202 ORIG_RAX: 00000000000000e6
RAX: ffffffffffffffda RBX: 00000000000001cc RCX: 00007f7a94ba34c3
RDX: 00007ffecab733a0 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00000000000f4240 R08: 00007ffecabca080 R09: 00007ffecabca0b0
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000000072f7
R13: 00007ffecab733dc R14: 00007ffecab733f0 R15: 00007ffecab733e0
</TASK>
BUG: scheduling while atomic: syz-executor957/294/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81528496>] remove_wait_queue+0x26/0x140 kernel/sched/wait.c:56
CPU: 1 PID: 294 Comm: syz-executor957 Tainted: G W 5.15.148-syzkaller-00704-g3802b45594e1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
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+0xd0b/0x1580 kernel/sched/core.c:6402
schedule+0x11f/0x1e0 kernel/sched/core.c:6595
freezable_schedule include/linux/freezer.h:197 [inline]
do_nanosleep+0x181/0x6a0 kernel/time/hrtimer.c:2044
hrtimer_nanosleep+0x1c5/0x3f0 kernel/time/hrtimer.c:2097
common_nsleep+0x91/0xb0 kernel/time/posix-timers.c:1267
__do_sys_clock_nanosleep kernel/time/posix-timers.c:1308 [inline]
__se_sys_clock_nanosleep+0x323/0x3b0 kernel/time/posix-timers.c:1285
__x64_sys_clock_nanosleep+0x9b/0xb0 kernel/time/posix-timers.c:1285
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:0x7f7a94ba34c3
Code: 00 00 00 00 00 66 90 83 ff 03 74 7b 83 ff 02 b8 fa ff ff ff 49 89 ca 0f 44 f8 80 3d be 1b 05 00 00 74 14 b8 e6 00 00 00 0f 05 <f7> d8 c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 28 48 89 54 24 10
RSP: 002b:00007ffecab73388 EFLAGS: 00000202 ORIG_RAX: 00000000000000e6
RAX: ffffffffffffffda RBX: 000000000000021a RCX: 00007f7a94ba34c3
RDX: 00007ffecab733a0 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00000000000f4240 R08: 00007ffecabca080 R09: 00007ffecabca0b0
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000000079c4
R13: 00007ffecab733dc R14: 00007ffecab733f0 R15: 00007ffecab733e0
</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

unread,
Feb 7, 2024, 10:49:27 PMFeb 7
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6053d8ffd476 UPSTREAM: arm64: scs: Disable LTO for SCS pat..
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=1384d138180000
kernel config: https://syzkaller.appspot.com/x/.config?x=54c503ca94c7e582
dashboard link: https://syzkaller.appspot.com/bug?extid=8bf134269eb79af54f90
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=172d0a38180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17100118180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/61cf81b4c37d/disk-6053d8ff.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/145e70f14225/vmlinux-6053d8ff.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a9261ee732bb/bzImage-6053d8ff.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8bf134...@syzkaller.appspotmail.com

BUG: scheduling while atomic: syz-executor337/291/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81565366>] remove_wait_queue+0x26/0x140 kernel/sched/wait.c:55
CPU: 1 PID: 291 Comm: syz-executor337 Not tainted 6.1.68-syzkaller-00006-g6053d8ffd476 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
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
__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
schedule+0xc3/0x180 kernel/sched/core.c:6805
do_nanosleep+0x149/0x580 kernel/time/hrtimer.c:2044
hrtimer_nanosleep+0x1c5/0x3f0 kernel/time/hrtimer.c:2097
common_nsleep+0x91/0xb0 kernel/time/posix-timers.c:1267
__do_sys_clock_nanosleep kernel/time/posix-timers.c:1308 [inline]
__se_sys_clock_nanosleep+0x323/0x3b0 kernel/time/posix-timers.c:1285
__x64_sys_clock_nanosleep+0x9b/0xb0 kernel/time/posix-timers.c:1285
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fa1a6b1c4c3
Code: 00 00 00 00 00 66 90 83 ff 03 74 7b 83 ff 02 b8 fa ff ff ff 49 89 ca 0f 44 f8 80 3d be 1b 05 00 00 74 14 b8 e6 00 00 00 0f 05 <f7> d8 c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 28 48 89 54 24 10
RSP: 002b:00007fffa5042af8 EFLAGS: 00000202 ORIG_RAX: 00000000000000e6
RAX: ffffffffffffffda RBX: 0000000000000219 RCX: 00007fa1a6b1c4c3
RDX: 00007fffa5042b10 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00000000000f4240 R08: 00007fffa507e080 R09: 00007fffa507e0b0
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000005ea8
R13: 00007fffa5042b4c R14: 00007fffa5042b60 R15: 00007fffa5042b50
Reply all
Reply to author
Forward
0 new messages