syzbot


BUG: scheduling while atomic in __writeback_inodes_sb_nr

Status: auto-obsoleted due to no activity on 2024/08/03 14:42
Reported-by: syzbot+8a2777c1ab8065982ca9@syzkaller.appspotmail.com
First crash: 212d, last: 212d

Sample crash report:
EXT4-fs (loop0): unmounting filesystem.
BUG: scheduling while atomic: syz-executor.0/6240/0x00000003
Modules linked in:
Preemption disabled at:
[<ffffffff81e83c85>] spin_lock include/linux/spinlock.h:350 [inline]
[<ffffffff81e83c85>] kernfs_put+0x325/0x520 fs/kernfs/dir.c:559
CPU: 1 PID: 6240 Comm: syz-executor.0 Tainted: G        W          6.1.75-syzkaller-00089-g1794308d463f #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:5964
 schedule_debug kernel/sched/core.c:5991 [inline]
 __schedule+0xcf7/0x1550 kernel/sched/core.c:6626
 schedule+0xc3/0x180 kernel/sched/core.c:6809
 wb_wait_for_completion+0x14c/0x270 fs/fs-writeback.c:191
 __writeback_inodes_sb_nr+0x2ce/0x370 fs/fs-writeback.c:2653
 writeback_inodes_sb_nr fs/fs-writeback.c:2670 [inline]
 writeback_inodes_sb+0x74/0x80 fs/fs-writeback.c:2685
 sync_filesystem+0xa8/0x250 fs/sync.c:54
 ext4_quota_off+0xd5/0x3f0 fs/ext4/super.c:7018
 ext4_quota_off_umount fs/ext4/super.c:1176 [inline]
 ext4_put_super+0xd3/0xd60 fs/ext4/super.c:1221
 generic_shutdown_super+0x14f/0x370 fs/super.c:503
 kill_block_super+0x7e/0xe0 fs/super.c:1461
 deactivate_locked_super+0xad/0x110 fs/super.c:334
 deactivate_super+0xbe/0xf0 fs/super.c:365
 cleanup_mnt+0x485/0x510 fs/namespace.c:1186
 __cleanup_mnt+0x19/0x20 fs/namespace.c:1193
 task_work_run+0x24d/0x2e0 kernel/task_work.c:179
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0x94/0xa0 kernel/entry/common.c:171
 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:0x7f3bb5e7f3aa
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3bb6b74ef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffea RBX: 00007f3bb6b74f80 RCX: 00007f3bb5e7f3aa
RDX: 0000000020000040 RSI: 0000000020000000 RDI: 00007f3bb6b74f40
RBP: 0000000020000040 R08: 00007f3bb6b74f80 R09: 0000000000208008
R10: 0000000000208008 R11: 0000000000000202 R12: 0000000020000000
R13: 00007f3bb6b74f40 R14: 000000000000046d R15: 00000000200002c0
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/05 14:41 android14-6.1 1794308d463f 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1 BUG: scheduling while atomic in __writeback_inodes_sb_nr
* Struck through repros no longer work on HEAD.