[moderation] [udf?] BUG: unable to handle kernel paging request in udf_close_lvid

7 views
Skip to first unread message

syzbot

unread,
Nov 6, 2024, 6:58:23 AM11/6/24
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 11066801dd4b Merge tag 'linux_kselftest-fixes-6.12-rc6' of..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1424cb40580000
kernel config: https://syzkaller.appspot.com/x/.config?x=672325e7ab17fdf7
dashboard link: https://syzkaller.appspot.com/bug?extid=0cca8aa413d30b0f242c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ja...@suse.com linux-...@vger.kernel.org]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-11066801.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b062b193560b/vmlinux-11066801.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5b6da4ee7c42/bzImage-11066801.xz

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

loop0: detected capacity change from 0 to 2048
UDF-fs: INFO Mounting volume 'Li uxUDF', timestamp 2022/11/22 14:59 (1000)
loop0: detected capacity change from 2048 to 0
=======================================================
WARNING: The mand mount option has been deprecated and
and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================
syz.0.0: attempt to access beyond end of device
loop0: rw=2049, sector=128, nr_sectors = 1 limit=0
Buffer I/O error on dev loop0, logical block 128, lost sync page write
loop0: detected capacity change from 0 to 2047
BUG: unable to handle page fault for address: ffffed100c14200d
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 5ffcd067 P4D 5ffcd067 PUD 2fff7067 PMD 0
Oops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5324 Comm: syz.0.0 Not tainted 6.12.0-rc5-syzkaller-00299-g11066801dd4b #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:udf_close_lvid+0x14c/0x9a0 fs/udf/super.c:2090
Code: dc 49 83 c4 50 0f 84 f3 00 00 00 49 8d bf c0 00 00 00 48 89 7c 24 40 31 f6 e8 30 b6 a9 08 49 8d 7c 24 18 48 89 f8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 41 05 00 00 4c 89 7c 24 18 4c 89 74 24
RSP: 0018:ffffc9000d42fc00 EFLAGS: 00010a02
RAX: 1ffff1100c14200d RBX: ffff88804ca10000 RCX: 0000000000000001
RDX: 0000000000000000 RSI: ffffffff8c610840 RDI: ffff888060a10068
RBP: ffffc9000d42fcf0 R08: ffffffff901d09af R09: 1ffffffff203a135
R10: dffffc0000000000 R11: fffffbfff203a136 R12: ffff888060a10050
R13: dffffc0000000000 R14: 1ffff92001a85f8c R15: ffff888032acdc00
FS: 00007efd4acc36c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffed100c14200d CR3: 00000000407de000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
udf_reconfigure+0x315/0x490 fs/udf/super.c:676
reconfigure_super+0x445/0x880 fs/super.c:1083
vfs_cmd_reconfigure fs/fsopen.c:262 [inline]
vfs_fsconfig_locked fs/fsopen.c:291 [inline]
__do_sys_fsconfig fs/fsopen.c:472 [inline]
__se_sys_fsconfig+0xb68/0xf70 fs/fsopen.c:344
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7efd49f7e719
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:00007efd4acc3038 EFLAGS: 00000246 ORIG_RAX: 00000000000001af
RAX: ffffffffffffffda RBX: 00007efd4a135f80 RCX: 00007efd49f7e719
RDX: 0000000000000000 RSI: 0000000000000007 RDI: 0000000000000006
RBP: 00007efd49ff132e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007efd4a135f80 R15: 00007ffc6ac33be8
</TASK>
Modules linked in:
CR2: ffffed100c14200d
---[ end trace 0000000000000000 ]---
RIP: 0010:udf_close_lvid+0x14c/0x9a0 fs/udf/super.c:2090
Code: dc 49 83 c4 50 0f 84 f3 00 00 00 49 8d bf c0 00 00 00 48 89 7c 24 40 31 f6 e8 30 b6 a9 08 49 8d 7c 24 18 48 89 f8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 41 05 00 00 4c 89 7c 24 18 4c 89 74 24
RSP: 0018:ffffc9000d42fc00 EFLAGS: 00010a02
RAX: 1ffff1100c14200d RBX: ffff88804ca10000 RCX: 0000000000000001
RDX: 0000000000000000 RSI: ffffffff8c610840 RDI: ffff888060a10068
RBP: ffffc9000d42fcf0 R08: ffffffff901d09af R09: 1ffffffff203a135
R10: dffffc0000000000 R11: fffffbfff203a136 R12: ffff888060a10050
R13: dffffc0000000000 R14: 1ffff92001a85f8c R15: ffff888032acdc00
FS: 00007efd4acc36c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffed100c14200d CR3: 00000000407de000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 49 83 c4 50 add $0x50,%r12
4: 0f 84 f3 00 00 00 je 0xfd
a: 49 8d bf c0 00 00 00 lea 0xc0(%r15),%rdi
11: 48 89 7c 24 40 mov %rdi,0x40(%rsp)
16: 31 f6 xor %esi,%esi
18: e8 30 b6 a9 08 call 0x8a9b64d
1d: 49 8d 7c 24 18 lea 0x18(%r12),%rdi
22: 48 89 f8 mov %rdi,%rax
25: 48 c1 e8 03 shr $0x3,%rax
* 29: 42 0f b6 04 28 movzbl (%rax,%r13,1),%eax <-- trapping instruction
2e: 84 c0 test %al,%al
30: 0f 85 41 05 00 00 jne 0x577
36: 4c 89 7c 24 18 mov %r15,0x18(%rsp)
3b: 4c rex.WR
3c: 89 .byte 0x89
3d: 74 24 je 0x63


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

syzbot

unread,
Jan 31, 2025, 6:46:20 AM1/31/25
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages