[v6.1] general protection fault in mark_buffer_dirty_inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6741e066ec76 Linux 6.1.87
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1267190b180000
kernel config: https://syzkaller.appspot.com/x/.config?x=3fc2f61bd0ae457
dashboard link: https://syzkaller.appspot.com/bug?extid=04298256545591946a3d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b606a22ddf4b/disk-6741e066.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e31c21737449/vmlinux-6741e066.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee0cb8c049e9/bzImage-6741e066.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]
CPU: 0 PID: 5630 Comm: syz-executor.4 Not tainted 6.1.87-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:mark_buffer_dirty_inode+0x4c/0x300 fs/buffer.c:573
Code: ff 48 83 c5 30 48 89 e8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 ef e8 83 ef e0 ff 4c 8b 75 00 49 8d 6d 10 48 89 e8 48 c1 e8 03 <42> 80 3c 20 00 74 08 48 89 ef e8 65 ef e0 ff 48 8b 6d 00 48 83 c5
RSP: 0018:ffffc900036ff828 EFLAGS: 00010202
RAX: 0000000000000002 RBX: 0000000000000001 RCX: 0000000000040000
RDX: ffffc90010873000 RSI: 00000000000083d1 RDI: 00000000000083d2
RBP: 0000000000000010 R08: ffffffff82fe86a1 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: dffffc0000000000
R13: 0000000000000000 R14: ffff888055ca9050 R15: dffffc0000000000
FS: 00007fc40a9f66c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000156e9000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
udf_rename+0xb58/0x14d0 fs/udf/namei.c:1190
vfs_rename+0xd32/0x10f0 fs/namei.c:4876
do_renameat2+0xde0/0x1440 fs/namei.c:5029
__do_sys_renameat2 fs/namei.c:5062 [inline]
__se_sys_renameat2 fs/namei.c:5059 [inline]
__x64_sys_renameat2+0xce/0xe0 fs/namei.c:5059
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc40be7dea9
Code: 28 00 00 00 75 05 48 83 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
RSP: 002b:00007fc40a9f60c8 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007fc40bfac050 RCX: 00007fc40be7dea9
RDX: 0000000000000005 RSI: 0000000020000100 RDI: 0000000000000005
RBP: 00007fc40beca4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000140 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fc40bfac050 R15: 00007ffd471e7e38
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:mark_buffer_dirty_inode+0x4c/0x300 fs/buffer.c:573
Code: ff 48 83 c5 30 48 89 e8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 ef e8 83 ef e0 ff 4c 8b 75 00 49 8d 6d 10 48 89 e8 48 c1 e8 03 <42> 80 3c 20 00 74 08 48 89 ef e8 65 ef e0 ff 48 8b 6d 00 48 83 c5
RSP: 0018:ffffc900036ff828 EFLAGS: 00010202
RAX: 0000000000000002 RBX: 0000000000000001 RCX: 0000000000040000
RDX: ffffc90010873000 RSI: 00000000000083d1 RDI: 00000000000083d2
RBP: 0000000000000010 R08: ffffffff82fe86a1 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: dffffc0000000000
R13: 0000000000000000 R14: ffff888055ca9050 R15: dffffc0000000000
FS: 00007fc40a9f66c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff520f2f98 CR3: 00000000156e9000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 48 83 c5 30 add $0x30,%rbp
4: 48 89 e8 mov %rbp,%rax
7: 48 c1 e8 03 shr $0x3,%rax
b: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1)
10: 74 08 je 0x1a
12: 48 89 ef mov %rbp,%rdi
15: e8 83 ef e0 ff call 0xffe0ef9d
1a: 4c 8b 75 00 mov 0x0(%rbp),%r14
1e: 49 8d 6d 10 lea 0x10(%r13),%rbp
22: 48 89 e8 mov %rbp,%rax
25: 48 c1 e8 03 shr $0x3,%rax
* 29: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1) <-- trapping instruction
2e: 74 08 je 0x38
30: 48 89 ef mov %rbp,%rdi
33: e8 65 ef e0 ff call 0xffe0ef9d
38: 48 8b 6d 00 mov 0x0(%rbp),%rbp
3c: 48 rex.W
3d: 83 .byte 0x83
3e: c5 .byte 0xc5


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