syzbot


BUG: scheduling while atomic in ext4_buffered_write_iter

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

Sample crash report:
BUG: scheduling while atomic: syz-executor.1/13661/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81e7f78a>] spin_lock include/linux/spinlock.h:363 [inline]
[<ffffffff81e7f78a>] ext4_da_reserve_space+0x13a/0x450 fs/ext4/inode.c:1492
CPU: 1 PID: 13661 Comm: syz-executor.1 Tainted: G        W         5.15.148-syzkaller-00718-g993bed180178 #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/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
 schedule+0x11f/0x1e0 kernel/sched/core.c:6595
 rwsem_down_write_slowpath+0xde4/0x1d70 kernel/locking/rwsem.c:1207
 __down_write_common kernel/locking/rwsem.c:1341 [inline]
 __down_write kernel/locking/rwsem.c:1350 [inline]
 down_write+0x29/0x30 kernel/locking/rwsem.c:1603
 inode_lock include/linux/fs.h:806 [inline]
 ext4_buffered_write_iter+0xa9/0x610 fs/ext4/file.c:264
 ext4_file_write_iter+0x443/0x1c80
 __kernel_write+0x5ab/0xa60 fs/read_write.c:539
 __dump_emit+0x261/0x3a0 fs/coredump.c:875
 dump_emit+0x381/0x3f0 fs/coredump.c:912
 dump_user_range+0x86/0x1c0 fs/coredump.c:949
 elf_core_dump+0x3663/0x3e80 fs/binfmt_elf.c:2285
 do_coredump+0x1834/0x3050 fs/coredump.c:826
 get_signal+0x4c8/0x1630 kernel/signal.c:2882
 arch_do_signal_or_restart+0xbd/0x1680 arch/x86/kernel/signal.c:867
 handle_signal_work kernel/entry/common.c:148 [inline]
 exit_to_user_mode_loop+0xa0/0xe0 kernel/entry/common.c:172
 exit_to_user_mode_prepare+0x5a/0xa0 kernel/entry/common.c:208
 irqentry_exit_to_user_mode+0x9/0x20 kernel/entry/common.c:314
 irqentry_exit+0x12/0x40 kernel/entry/common.c:405
 exc_general_protection+0x327/0x4b0 arch/x86/kernel/traps.c:562
 asm_exc_general_protection+0x27/0x30 arch/x86/include/asm/idtentry.h:562
RIP: 0033:0x7f0b6f71ce71
Code: c4 28 c3 e8 e1 20 00 00 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 73 01 <c3> 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f
RSP: 002b:0000000020000530 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007f0b6f84af80 RCX: 00007f0b6f71ce69
RDX: 0000000020000300 RSI: 0000000020000530 RDI: 0000000003000080
RBP: 00007f0b6f76947a R08: 00000000200005c0 R09: 00000000200005c0
R10: 0000000020000580 R11: 0000000000000202 R12: 0000000000000000
R13: 000000000000000b R14: 00007f0b6f84af80 R15: 00007ffcbfca6968
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/06 19:58 android13-5.15-lts 993bed180178 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in ext4_buffered_write_iter
* Struck through repros no longer work on HEAD.