syzbot


BUG: scheduling while atomic in ext4_buffered_write_iter

Status: auto-obsoleted due to no activity on 2024/07/06 13:13
Reported-by: syzbot+141ed1e35f22d9b37fa1@syzkaller.appspotmail.com
First crash: 229d, last: 229d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-15 BUG: scheduling while atomic in ext4_buffered_write_iter 1 230d 230d 0/2 auto-obsoleted due to no activity on 2024/07/05 20:06

Sample crash report:
BUG: scheduling while atomic: syz-executor.4/26016/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81b74c44>] rmqueue_pcplist mm/page_alloc.c:3897 [inline]
[<ffffffff81b74c44>] rmqueue mm/page_alloc.c:3946 [inline]
[<ffffffff81b74c44>] get_page_from_freelist+0x554/0x2870 mm/page_alloc.c:4398
CPU: 1 PID: 26016 Comm: syz-executor.4 Tainted: G        W          6.1.75-syzkaller-00123-g60534eef4739 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/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
 __schedule_bug+0x195/0x260 kernel/sched/core.c:5960
 schedule_debug kernel/sched/core.c:5987 [inline]
 __schedule+0xcf7/0x1550 kernel/sched/core.c:6622
 schedule+0xc3/0x180 kernel/sched/core.c:6805
 rwsem_down_write_slowpath+0xddf/0x20a0 kernel/locking/rwsem.c:1227
 __down_write_common kernel/locking/rwsem.c:1357 [inline]
 __down_write kernel/locking/rwsem.c:1366 [inline]
 down_write+0x21/0x30 kernel/locking/rwsem.c:1619
 inode_lock include/linux/fs.h:758 [inline]
 ext4_buffered_write_iter+0xa9/0x640 fs/ext4/file.c:279
 ext4_file_write_iter+0x194/0x1570
 __kernel_write_iter+0x2ff/0x710 fs/read_write.c:517
 dump_emit_page fs/coredump.c:881 [inline]
 dump_user_range+0x469/0x6f0 fs/coredump.c:908
 elf_core_dump+0x3746/0x4030 fs/binfmt_elf.c:2312
 do_coredump+0x1909/0x2730 fs/coredump.c:755
 get_signal+0x13ff/0x1820 kernel/signal.c:2865
 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
 irqentry_exit_to_user_mode+0x9/0x20 kernel/entry/common.c:310
 irqentry_exit+0x12/0x40 kernel/entry/common.c:413
 exc_page_fault+0x4f3/0x700 arch/x86/mm/fault.c:1565
 asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7f9597e28777
Code: 0a 0a 00 e8 3b fb ff ff 48 8d 3d 8f 0a 0a 00 e8 2f fb ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 53 89 fb 48 83 ec 10 <64> 8b 04 25 ac ff ff ff 85 c0 74 2a 89 fe 31 c0 bf 3c 00 00 00 e8
RSP: 002b:00007f9598c101e0 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 000000000000000b RCX: 00007f9597e7de69
RDX: 00007f9598c10200 RSI: 00007f9598c10330 RDI: 000000000000000b
RBP: 00007f9597eca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000
R13: 000000000000000b R14: 00007f9597fabf80 R15: 00007ffdfbabd268
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/07 13:11 android14-6.1 60534eef4739 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: scheduling while atomic in ext4_buffered_write_iter
* Struck through repros no longer work on HEAD.