general protection fault in mark_buffer_dirty_inode (2)

6 views
Skip to first unread message

syzbot

unread,
Nov 27, 2022, 10:52:29 PM11/27/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16988d75880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=593005f49ea4c3bececa
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11151975880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=150fe9bb880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/fb33acd91766/mount_0.gz

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

UDF-fs: error (device loop0): udf_read_tagged: read failed, block=256, location=256
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000)
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 8102 Comm: syz-executor663 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:mark_buffer_dirty_inode+0x51/0x3c0 fs/buffer.c:547
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 ec 02 00 00 48 8d 7b 10 48 8b 6d 30 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 b5 02 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b
RSP: 0018:ffff8880948e79d0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff82700bb8
RDX: 0000000000000002 RSI: ffffffff81b05229 RDI: 0000000000000010
RBP: ffff88808ac1d328 R08: 0000000000000001 R09: 0000000000000003
R10: 0000000000000001 R11: 0000000000000000 R12: ffff88808ac1d670
R13: 0000000000000001 R14: ffff88808ac1d120 R15: ffff8880b0c11340
FS: 00007fac492d0700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fac492d0718 CR3: 00000000abba7000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
udf_rename+0x804/0x1270 fs/udf/namei.c:1202
vfs_rename+0x67e/0x1bc0 fs/namei.c:4479
do_renameat2+0xb59/0xc70 fs/namei.c:4629
__do_sys_rename fs/namei.c:4675 [inline]
__se_sys_rename fs/namei.c:4673 [inline]
__x64_sys_rename+0x5d/0x80 fs/namei.c:4673
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fac517355a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 15 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fac492d02f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fac517ba7b0 RCX: 00007fac517355a9
RDX: 00007fac492d0700 RSI: 0000000020000100 RDI: 0000000020000040
RBP: 0030656c69662f2e R08: 00007fac492d0700 R09: 0000000000000000
R10: 00007fac492d0700 R11: 0000000000000246 R12: 00007fac517870c0
R13: 0000000020000580 R14: f6f2cbf92df09e20 R15: 00007fac517ba7b8
Modules linked in:
---[ end trace 1bd3fd187b995441 ]---
RIP: 0010:mark_buffer_dirty_inode+0x51/0x3c0 fs/buffer.c:547
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 ec 02 00 00 48 8d 7b 10 48 8b 6d 30 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 b5 02 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b
RSP: 0018:ffff8880948e79d0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff82700bb8
RDX: 0000000000000002 RSI: ffffffff81b05229 RDI: 0000000000000010
RBP: ffff88808ac1d328 R08: 0000000000000001 R09: 0000000000000003
R10: 0000000000000001 R11: 0000000000000000 R12: ffff88808ac1d670
R13: 0000000000000001 R14: ffff88808ac1d120 R15: ffff8880b0c11340
FS: 00007fac492d0700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fac51776c80 CR3: 00000000abba7000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 48 89 fa mov %rdi,%rdx
3: 48 c1 ea 03 shr $0x3,%rdx
7: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
b: 0f 85 ec 02 00 00 jne 0x2fd
11: 48 8d 7b 10 lea 0x10(%rbx),%rdi
15: 48 8b 6d 30 mov 0x30(%rbp),%rbp
19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
20: fc ff df
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 b5 02 00 00 jne 0x2e9
34: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
3b: fc ff df
3e: 4c rex.WR
3f: 8b .byte 0x8b


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages