[Android 5.10] kernel BUG in mark_buffer_dirty_inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 911f602c2237 Merge 5.10.244 into android13-5.10-lts
git tree: android13-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=15559d34580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5193c33e6e6dcf8b
dashboard link: https://syzkaller.appspot.com/bug?extid=ab5d2ec66a8df4e576ed
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=135abce2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=104042e2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/64ba8a538674/disk-911f602c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7fa800536e61/vmlinux-911f602c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/42e648d2ee3c/bzImage-911f602c.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3dd7c276d42c/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=12631142580000)

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

------------[ cut here ]------------
kernel BUG at fs/buffer.c:581!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 384 Comm: syz.1.18 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:mark_buffer_dirty_inode+0x308/0x310 fs/buffer.c:581
Code: 74 08 4c 89 f7 e8 78 32 ea ff 4d 89 2e 48 8b 7d a8 e8 2c 92 c4 02 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 68 44 b0 ff <0f> 0b 66 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 54 53 48 89 fb
RSP: 0018:ffffc90000dd7770 EFLAGS: 00010293
RAX: ffffffff81b361a8 RBX: ffff88810044b590 RCX: ffff888111b213c0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff888111b213c0
RBP: ffffc90000dd77c8 R08: dffffc0000000000 R09: fffff9400088be79
R10: fffff9400088be79 R11: 1ffffd400088be78 R12: dffffc0000000000
R13: ffff88810919c290 R14: 1ffff11021233869 R15: ffff88810919c348
FS: 000055556e0f2500(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4ebccf4000 CR3: 00000001118dd000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__ext4_handle_dirty_metadata+0x25e/0x7f0 fs/ext4/ext4_jbd2.c:362
ext4_xattr_release_block+0x72e/0x9f0 fs/ext4/xattr.c:1303
ext4_xattr_delete_inode+0xa6f/0xbf0 fs/ext4/xattr.c:2952
ext4_evict_inode+0x10d3/0x1760 fs/ext4/inode.c:300
evict+0x478/0x910 fs/inode.c:612
iput_final fs/inode.c:1736 [inline]
iput+0x638/0x7c0 fs/inode.c:1762
dentry_unlink_inode+0x2cf/0x380 fs/dcache.c:378
__dentry_kill+0x44f/0x650 fs/dcache.c:583
dentry_kill+0xc0/0x2a0 fs/dcache.c:-1
dput+0x42/0x80 fs/dcache.c:883
__fput+0x4fe/0x770 fs/file_table.c:294
____fput+0x15/0x20 fs/file_table.c:314
task_work_run+0x127/0x190 kernel/task_work.c:189
tracehook_notify_resume include/linux/tracehook.h:188 [inline]
exit_to_user_mode_loop+0xcb/0xe0 kernel/entry/common.c:172
exit_to_user_mode_prepare+0x76/0xa0 kernel/entry/common.c:199
syscall_exit_to_user_mode+0x1d/0x40 kernel/entry/common.c:274
do_syscall_64+0x3d/0x40 arch/x86/entry/common.c:56
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f3a9e2faec9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffec684a638 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 0000000000006d16 RCX: 00007f3a9e2faec9
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000001 R09: 00000006c684a92f
R10: 0000001b32420000 R11: 0000000000000246 R12: 00007f3a9e551fac
R13: 00007f3a9e551fa0 R14: ffffffffffffffff R15: 0000000000000005
Modules linked in:
---[ end trace a9398cb23ecff67c ]---
RIP: 0010:mark_buffer_dirty_inode+0x308/0x310 fs/buffer.c:581
Code: 74 08 4c 89 f7 e8 78 32 ea ff 4d 89 2e 48 8b 7d a8 e8 2c 92 c4 02 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 68 44 b0 ff <0f> 0b 66 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 54 53 48 89 fb
RSP: 0018:ffffc90000dd7770 EFLAGS: 00010293
RAX: ffffffff81b361a8 RBX: ffff88810044b590 RCX: ffff888111b213c0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff888111b213c0
RBP: ffffc90000dd77c8 R08: dffffc0000000000 R09: fffff9400088be79
R10: fffff9400088be79 R11: 1ffffd400088be78 R12: dffffc0000000000
R13: ffff88810919c290 R14: 1ffff11021233869 R15: ffff88810919c348
FS: 000055556e0f2500(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff78b9d000 CR3: 00000001118dd000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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