[v5.15] BUG: unable to handle kernel paging request in ocfs2_buffer_cached

0 views
Skip to first unread message

syzbot

unread,
Sep 26, 2024, 11:51:24 PMSep 26
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11c5f627980000
kernel config: https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link: https://syzkaller.appspot.com/bug?extid=3385eeaba6f50fd0925d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/22ee27cb312d/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz

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

(syz.2.2347,14371,1):ocfs2_read_blocks:240 ERROR: status = -12
Unable to handle kernel paging request at virtual address dfff800000000003
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000003] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 14371 Comm: syz.2.2347 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_buffer_cached+0xc0/0x8f4 fs/ocfs2/uptodate.c:237
lr : ocfs2_metadata_cache_owner fs/ocfs2/uptodate.c:60 [inline]
lr : ocfs2_buffer_cached+0xb4/0x8f4 fs/ocfs2/uptodate.c:236
sp : ffff800020406200
x29: ffff800020406220 x28: ffff700004080c58 x27: ffff8000204068c0
x26: 1fffe0001daa32ce x25: dfff800000000000 x24: 0000000000000003
x23: 0000000000000000 x22: 0000000000000042 x21: ffff800011fb6a60
x20: 0000000000000018 x19: ffff0000ed519670 x18: ffff800020405ec0
x17: 0000000000000002 x16: ffff80000830532c x15: 0000000000045241
x14: 000000006cc0c3c6 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000003ee25 x10: ffff80002323a000 x9 : 1fffe0001daa31c8
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff800017958148 x4 : 0000000000000008 x3 : ffff80000830545c
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000042
Call trace:
ocfs2_buffer_cached+0xc0/0x8f4 fs/ocfs2/uptodate.c:237
ocfs2_set_buffer_uptodate+0xb4/0x11a0 fs/ocfs2/uptodate.c:474
ocfs2_read_blocks+0xe84/0x1628 fs/ocfs2/buffer_head_io.c:392
ocfs2_read_virt_blocks+0x3fc/0x960 fs/ocfs2/extent_map.c:1010
ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline]
ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline]
ocfs2_find_entry+0x3ac/0x2450 fs/ocfs2/dir.c:1080
ocfs2_find_files_on_disk+0x10c/0x3d0 fs/ocfs2/dir.c:1982
ocfs2_lookup_ino_from_name+0xb8/0x1d4 fs/ocfs2/dir.c:2004
_ocfs2_get_system_file_inode fs/ocfs2/sysfile.c:136 [inline]
ocfs2_get_system_file_inode+0x2c8/0x6b8 fs/ocfs2/sysfile.c:112
ocfs2_init_global_system_inodes+0x2bc/0x618 fs/ocfs2/super.c:458
ocfs2_initialize_super fs/ocfs2/super.c:2276 [inline]
ocfs2_fill_super+0x394c/0x498c fs/ocfs2/super.c:995
mount_bdev+0x274/0x370 fs/super.c:1398
ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1187
legacy_get_tree+0xd4/0x16c fs/fs_context.c:611
vfs_get_tree+0x90/0x274 fs/super.c:1528
do_new_mount+0x278/0x8fc fs/namespace.c:3005
path_mount+0x594/0x101c fs/namespace.c:3335
do_mount fs/namespace.c:3348 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount fs/namespace.c:3533 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3533
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d63f0100 91006294 aa0003f6 d343fe98 (38796b08)
---[ end trace 4a632ac076e03165 ]---
----------------
Code disassembly (best guess):
0: d63f0100 blr x8
4: 91006294 add x20, x20, #0x18
8: aa0003f6 mov x22, x0
c: d343fe98 lsr x24, x20, #3
* 10: 38796b08 ldrb w8, [x24, x25] <-- trapping instruction


---
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,
Sep 27, 2024, 12:05:30 AMSep 27
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=115baaa9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link: https://syzkaller.appspot.com/bug?extid=3385eeaba6f50fd0925d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e8159f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d5f627980000
mounted in repro: https://storage.googleapis.com/syzbot-assets/cd69e56c2b86/mount_0.gz

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

and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================
(syz-executor214,4015,1):ocfs2_read_blocks:240 ERROR: status = -12
Unable to handle kernel paging request at virtual address dfff800000000003
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000003] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4015 Comm: syz-executor214 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_buffer_cached+0xc0/0x8f4 fs/ocfs2/uptodate.c:237
lr : ocfs2_metadata_cache_owner fs/ocfs2/uptodate.c:60 [inline]
lr : ocfs2_buffer_cached+0xb4/0x8f4 fs/ocfs2/uptodate.c:236
sp : ffff80001fd16200
x29: ffff80001fd16220 x28: ffff700003fa2c58 x27: ffff80001fd168c0
x26: 1fffe0001c28f2ce x25: dfff800000000000 x24: 0000000000000003
x23: 0000000000000000 x22: 0000000000000042 x21: ffff800011fb6a60
x20: 0000000000000018 x19: ffff0000e1479670 x18: ffff80001fd15ec0
x17: 0000000000000000 x16: ffff80000830532c x15: 000000000000b999
x14: 000000006cc0c3c6 x13: dfff800000000000 x12: ffff700003fa2c20
x11: 0000000000000001 x10: 0000000000000000 x9 : 1fffe0001c28f1c8
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff80001778bb70 x4 : 0000000000000008 x3 : ffff80000830545c
---[ end trace 95d5d1d0968ad883 ]---
----------------
Code disassembly (best guess):
0: d63f0100 blr x8
4: 91006294 add x20, x20, #0x18
8: aa0003f6 mov x22, x0
c: d343fe98 lsr x24, x20, #3
* 10: 38796b08 ldrb w8, [x24, x25] <-- trapping instruction


---
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.
Reply all
Reply to author
Forward
0 new messages