Hello, syzbot found the following issue on: HEAD commit: 0d8d44db295c Merge tag 'for-6.15-rc5-tag' of git://git.ker.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1513e8f4580000 kernel config: https://syzkaller.appspot.com/x/.config?x=91c351a0f6229e67 dashboard link: https://syzkaller.appspot.com/bug?extid=2327bccb02eef9291c1c compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103904d4580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1313e8f4580000 Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-0d8d44db.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/560a4d87ba79/vmlinux-0d8d44db.xz kernel image: https://storage.googleapis.com/syzbot-assets/2767d37c74f0/bzImage-0d8d44db.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/237a200bd337/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+2327bccb02eef9291c1c@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5313 at fs/buffer.c:1186 mark_buffer_dirty+0x2a9/0x410 fs/buffer.c:1186 Modules linked in: CPU: 0 UID: 0 PID: 5313 Comm: syz-executor161 Not tainted 6.15.0-rc5-syzkaller-00032-g0d8d44db295c #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:mark_buffer_dirty+0x2a9/0x410 fs/buffer.c:1186 Code: 4c 89 f7 e8 79 0d de ff 49 8b 3e be 20 00 00 00 5b 41 5c 41 5e 41 5f 5d e9 c4 34 fc ff e8 cf 18 7c ff eb 8c e8 c8 18 7c ff 90 <0f> 0b 90 e9 95 fd ff ff e8 ba 18 7c ff 90 0f 0b 90 e9 bf fd ff ff RSP: 0018:ffffc9000d26fce0 EFLAGS: 00010293 RAX: ffffffff8243b788 RBX: ffff888047493ae0 RCX: ffff88801f494880 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002 RBP: 1ffff11003bf1001 R08: ffff888047493ae7 R09: 1ffff11008e9275c R10: dffffc0000000000 R11: ffffed1008e9275d R12: 0000000000000000 R13: dffffc0000000000 R14: ffffffff829851d0 R15: ffff88801df88780 FS: 00005555720f8480(0000) GS:ffff88808d6cb000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffedcb1fd28 CR3: 00000000432ad000 CR4: 0000000000352ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> hfs_put_super+0x49/0x60 fs/hfs/super.c:51 generic_shutdown_super+0x132/0x2c0 fs/super.c:642 kill_block_super+0x44/0x90 fs/super.c:1710 deactivate_locked_super+0xb9/0x130 fs/super.c:473 cleanup_mnt+0x425/0x4c0 fs/namespace.c:1435 task_work_run+0x1d1/0x260 kernel/task_work.c:227 resume_user_mode_work+0x5e/0x80 include/linux/resume_user_mode.h:50 exit_to_user_mode_loop kernel/entry/common.c:114 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x9a/0x120 kernel/entry/common.c:218 do_syscall_64+0x103/0x210 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f0854de79f7 Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 RSP: 002b:00007ffedcb1ed38 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f0854de79f7 RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffedcb1edf0 RBP: 00007ffedcb1edf0 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000ffffffff R11: 0000000000000202 R12: 00007ffedcb1fe60 R13: 00005555720f97c0 R14: 431bde82d7b634db R15: 00007ffedcb1fe80 </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 syzkaller@xxxxxxxxxxxxxxxx. 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
