Hello, syzbot found the following issue on: HEAD commit: 6d464646530f Merge branch 'for-next/core' into for-kernelci git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=17a49603880000 kernel config: https://syzkaller.appspot.com/x/.config?x=23eec5c79c22aaf8 dashboard link: https://syzkaller.appspot.com/bug?extid=a313c6d1d9ef87de2a66 compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14382015880000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f791c3880000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/f22d29413625/disk-6d464646.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/389f0a5f1a4a/vmlinux-6d464646.xz kernel image: https://storage.googleapis.com/syzbot-assets/48ddb02d82da/Image-6d464646.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/23c8423bc069/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+a313c6d1d9ef87de2a66@xxxxxxxxxxxxxxxxxxxxxxxxx and is ignored by this kernel. Remove the mand option from the mount to silence this warning. ======================================================= ------------[ cut here ]------------ kernel BUG at fs/hfsplus/xattr.c:175! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 0 PID: 3072 Comm: syz-executor864 Not tainted 6.1.0-rc6-syzkaller-32662-g6d464646530f #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022 pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : hfsplus_create_attributes_file+0x6d4/0x6fc fs/hfsplus/xattr.c:175 lr : hfsplus_create_attributes_file+0x6d4/0x6fc fs/hfsplus/xattr.c:175 sp : ffff80000fbab650 x29: ffff80000fbab670 x28: 0000000000000000 x27: ffff0000c6616000 x26: ffff0000c94e6000 x25: 000000000000002e x24: 0000000000000080 x23: 0000000000000000 x22: 0000000000010000 x21: 0000000000000001 x20: ffff0000cb7fa8b0 x19: ffff0000c6616038 x18: 00000000000000c0 x17: 0000000000000000 x16: ffff80000dbe6158 x15: ffff0000c7df0000 x14: 00000000000000b8 x13: 00000000ffffffff x12: ffff0000c7df0000 x11: ff808000088f78f0 x10: 0000000000000000 x9 : ffff8000088f78f0 x8 : ffff0000c7df0000 x7 : ffff8000085f9554 x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000 x2 : 0000000000000001 x1 : 0000000000010000 x0 : 0000000000000000 Call trace: hfsplus_create_attributes_file+0x6d4/0x6fc fs/hfsplus/xattr.c:175 __hfsplus_setxattr+0x180/0x4e8 fs/hfsplus/xattr.c:331 hfsplus_initxattrs+0xac/0x130 fs/hfsplus/xattr_security.c:59 security_inode_init_security+0x208/0x278 security/security.c:1119 hfsplus_init_security+0x40/0x54 fs/hfsplus/xattr_security.c:71 hfsplus_mknod+0x128/0x1bc fs/hfsplus/dir.c:498 hfsplus_create+0x40/0x54 fs/hfsplus/dir.c:523 lookup_open fs/namei.c:3413 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x804/0x11c4 fs/namei.c:3710 do_filp_open+0xdc/0x1b8 fs/namei.c:3740 do_sys_openat2+0xb8/0x22c fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_openat fs/open.c:1342 [inline] __se_sys_openat fs/open.c:1337 [inline] __arm64_sys_openat+0xb0/0xe0 fs/open.c:1337 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall arch/arm64/kernel/syscall.c:52 [inline] el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584 Code: d4210000 97e6b81d d4210000 97e6b81b (d4210000) ---[ end trace 0000000000000000 ]--- --- 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 syzkaller@xxxxxxxxxxxxxxxx. 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
