[v5.15] WARNING in hfsplus_cat_read_inode

0 views
Skip to first unread message

syzbot

unread,
Mar 20, 2023, 11:51:09 PM3/20/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 8020ae3c051d Linux 5.15.103
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1335ef16c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d4215fb4040f8f8d
dashboard link: https://syzkaller.appspot.com/bug?extid=b9a563c9e91fe46ab024
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/857e17de0f0a/disk-8020ae3c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9efc49fcd441/vmlinux-8020ae3c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f14c38b6bfa7/bzImage-8020ae3c.xz

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

WARNING: CPU: 0 PID: 2233 at fs/hfsplus/inode.c:532 hfsplus_cat_read_inode+0xa97/0xee0
Modules linked in:
CPU: 0 PID: 2233 Comm: syz-executor.1 Not tainted 5.15.103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:hfsplus_cat_read_inode+0xa97/0xee0 fs/hfsplus/inode.c:532
Code: 3b 9f 8a e8 54 e0 e1 07 b8 fb ff ff ff 49 bc 00 00 00 00 00 fc ff df eb 82 e8 55 a6 40 ff 0f 0b e9 07 f7 ff ff e8 49 a6 40 ff <0f> 0b e9 4f fa ff ff 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 45 f6
RSP: 0018:ffffc90005b273a0 EFLAGS: 00010246
RAX: ffffffff823fd287 RBX: ffffc90005b27778 RCX: 0000000000040000
RDX: ffffc90006d75000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffffc90005b276f0 R08: ffffffff823fccc7 R09: ffffffff823fc92d
R10: 0000000000000002 R11: ffff888022623a00 R12: ffffc90005b27790
R13: 1ffff92000b64eef R14: 0000000000000002 R15: ffffc90005b27400
FS: 00007f8956359700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c030162020 CR3: 000000003cfac000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
hfsplus_iget+0x586/0x640 fs/hfsplus/super.c:84
hfsplus_fill_super+0xca4/0x1c90 fs/hfsplus/super.c:503
mount_bdev+0x26d/0x3a0 fs/super.c:1369
legacy_get_tree+0xeb/0x180 fs/fs_context.c:610
vfs_get_tree+0x88/0x270 fs/super.c:1499
do_new_mount+0x28b/0xad0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8957de862a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 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:00007f8956358f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000649 RCX: 00007f8957de862a
RDX: 0000000020000100 RSI: 0000000020000080 RDI: 00007f8956358fe0
RBP: 00007f8956359020 R08: 00007f8956359020 R09: 0000000001800000
R10: 0000000001800000 R11: 0000000000000202 R12: 0000000020000100
R13: 0000000020000080 R14: 00007f8956358fe0 R15: 0000000020000000
</TASK>


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

unread,
May 12, 2023, 6:55:44 AM5/12/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: b0ece631f84a Linux 5.15.111
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11d97cfa280000
kernel config: https://syzkaller.appspot.com/x/.config?x=db3750b003ff805e
dashboard link: https://syzkaller.appspot.com/bug?extid=b9a563c9e91fe46ab024
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cec252280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f7ad42280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eded75b6c3f9/disk-b0ece631.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/20e5ae802010/vmlinux-b0ece631.xz
kernel image: https://storage.googleapis.com/syzbot-assets/05d665c869f3/Image-b0ece631.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/aad27a717aea/mount_0.gz

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

loop0: detected capacity change from 0 to 1024
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3962 at fs/hfsplus/inode.c:532 hfsplus_cat_read_inode+0x864/0xc38 fs/hfsplus/inode.c:532
Modules linked in:
CPU: 0 PID: 3962 Comm: syz-executor100 Not tainted 5.15.111-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfsplus_cat_read_inode+0x864/0xc38 fs/hfsplus/inode.c:532
lr : hfsplus_cat_read_inode+0x864/0xc38 fs/hfsplus/inode.c:532
sp : ffff80001af470e0
x29: ffff80001af473e0 x28: 1ffff000035e8e93 x27: 1ffff000035e8e95
x26: dfff800000000000 x25: ffff7000035e8e20 x24: 0000000000000002
x23: 000000000000004e x22: ffff80001af47498 x21: ffff80001af474ac
x20: ffff80001af47120 x19: ffff0000d7ef1cb0 x18: 0000000000000000
x17: ff80800008f98ff0 x16: 0000000000000000 x15: ffff800008f98ff0
x14: 0000000000000002 x13: ffffffffffffffff x12: 0000000000000000
x11: ff80800008f9974c x10: 0000000000000000 x9 : ffff800008f9974c
x8 : ffff0000d8b8d1c0 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff80001af47062 x4 : ffff000178c93032 x3 : ffff800008fac1d0
x2 : 0000000000000002 x1 : 000000000000004e x0 : 00000000000000f8
Call trace:
hfsplus_cat_read_inode+0x864/0xc38 fs/hfsplus/inode.c:532
hfsplus_iget+0x4ac/0x570 fs/hfsplus/super.c:84
hfsplus_fill_super+0x9c4/0x167c fs/hfsplus/super.c:503
mount_bdev+0x26c/0x368 fs/super.c:1378
hfsplus_mount+0x44/0x58 fs/hfsplus/super.c:641
legacy_get_tree+0xd4/0x16c fs/fs_context.c:610
vfs_get_tree+0x90/0x274 fs/super.c:1508
do_new_mount+0x25c/0x8c8 fs/namespace.c:2994
path_mount+0x590/0x104c fs/namespace.c:3324
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3522
__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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 16478
hardirqs last enabled at (16477): [<ffff800011a1bbd8>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
hardirqs last enabled at (16477): [<ffff800011a1bbd8>] _raw_spin_unlock_irqrestore+0xac/0x158 kernel/locking/spinlock.c:194
hardirqs last disabled at (16478): [<ffff800011943708>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (15862): [<ffff8000080300b4>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (15860): [<ffff800008030080>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace 588c9a726d7046a2 ]---


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