Hello, syzbot found the following issue on: HEAD commit: 707081b61156 Merge branch 'for-next/core', remote-tracking.. 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=1562c52d180000 kernel config: https://syzkaller.appspot.com/x/.config?x=caeac3f3565b057a dashboard link: https://syzkaller.appspot.com/bug?extid=b417f0468b73945887f0 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=14e74805180000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1613cca9180000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/6cad68bf7532/disk-707081b6.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/1a27e5400778/vmlinux-707081b6.xz kernel image: https://storage.googleapis.com/syzbot-assets/67dfc53755d0/Image-707081b6.gz.xz mounted in repro #1: https://storage.googleapis.com/syzbot-assets/f039597bec42/mount_0.gz mounted in repro #2: https://storage.googleapis.com/syzbot-assets/b3fe5cff7c96/mount_4.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+b417f0468b73945887f0@xxxxxxxxxxxxxxxxxxxxxxxxx jffs2: nextblock 0x0001d000, expected at 0001f000 jffs2: argh. node added in wrong place at 0x0001e03c(2) jffs2: nextblock 0x0001d000, expected at 0001f000 ------------[ cut here ]------------ kernel BUG at fs/jffs2/xattr.c:411! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 0 PID: 6173 Comm: syz-executor110 Not tainted 6.8.0-rc7-syzkaller-g707081b61156 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : unrefer_xattr_datum+0x3a8/0x3ac fs/jffs2/xattr.c:411 lr : unrefer_xattr_datum+0x3a8/0x3ac fs/jffs2/xattr.c:411 sp : ffff8000978575f0 x29: ffff800097857600 x28: 1fffe0001aaffe23 x27: 1fffe0001aaffe28 x26: dfff800000000000 x25: 1fffe0001aaffe24 x24: ffff0000d57ff120 x23: 0000000000000001 x22: ffff0000d57ff118 x21: ffff0000d7d3a000 x20: ffff0000d57ff100 x19: ffff0000d7d3a638 x18: 1fffe000367fff96 x17: ffff80008ec9d000 x16: ffff80008032116c x15: 0000000000000001 x14: 1ffff00011ea7bfa x13: 0000000000000000 x12: 0000000000000003 x11: 0000000000000001 x10: 0000000000ff0100 x9 : 0000000000000000 x8 : ffff0000d5131e00 x7 : ffff80008005fa20 x6 : ffff80008005fc1c x5 : ffff0000d6092c08 x4 : ffff800097857368 x3 : 0000000000000000 x2 : ffff0000d57ff118 x1 : 0000000000000001 x0 : 00000000000000ff Call trace: unrefer_xattr_datum+0x3a8/0x3ac fs/jffs2/xattr.c:411 do_jffs2_setxattr+0xde0/0x1158 jffs2_trusted_setxattr+0x4c/0x64 fs/jffs2/xattr_trusted.c:33 __vfs_setxattr+0x3d8/0x400 fs/xattr.c:201 __vfs_setxattr_noperm+0x110/0x528 fs/xattr.c:235 __vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:296 vfs_setxattr+0x1a8/0x344 fs/xattr.c:322 do_setxattr fs/xattr.c:630 [inline] setxattr+0x208/0x29c fs/xattr.c:653 path_setxattr+0x17c/0x258 fs/xattr.c:672 __do_sys_lsetxattr fs/xattr.c:695 [inline] __se_sys_lsetxattr fs/xattr.c:691 [inline] __arm64_sys_lsetxattr+0xbc/0xd8 fs/xattr.c:691 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 Code: aa1803e0 97c66b4c 17ffff47 97b31b25 (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. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title 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. 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
