[syzbot] [ocfs2?] memory leak in ocfs2_new_path_from_path

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4a0c9b339199 Merge tag 'probes-fixes-v6.18-rc4' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15fbca92580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cb128cd5cb439809
dashboard link: https://syzkaller.appspot.com/bug?extid=cfc7cab3bb6eaa7c4de2
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114be17c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bfd02a09ef4d/disk-4a0c9b33.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ed9a1334f973/vmlinux-4a0c9b33.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e503329437ee/bzImage-4a0c9b33.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/275c7c156b9c/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=11545084580000)

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

BUG: memory leak
unreferenced object 0xffff8881286c42a0 (size 96):
comm "syz.3.46", pid 6293, jiffies 4294945738
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 a0 0e 30 82 ff ff ff ff ..........0.....
88 b8 5b 2d 81 88 ff ff c0 f4 c3 2f 81 88 ff ff ..[-......./....
backtrace (crc f97a0cdc):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4975 [inline]
slab_alloc_node mm/slub.c:5280 [inline]
__kmalloc_cache_noprof+0x3a6/0x5b0 mm/slub.c:5758
kmalloc_noprof include/linux/slab.h:957 [inline]
kzalloc_noprof include/linux/slab.h:1094 [inline]
ocfs2_new_path fs/ocfs2/alloc.c:688 [inline]
ocfs2_new_path_from_path+0x4f/0x90 fs/ocfs2/alloc.c:702
ocfs2_get_left_path.constprop.0+0x182/0x390 fs/ocfs2/alloc.c:3491
ocfs2_merge_rec_left+0x426/0xe60 fs/ocfs2/alloc.c:3543
ocfs2_try_to_merge_extent+0x3cb/0xe90 fs/ocfs2/alloc.c:3794
ocfs2_split_extent+0xd2e/0x1330 fs/ocfs2/alloc.c:5139
ocfs2_change_extent_flag+0x2ed/0x720 fs/ocfs2/alloc.c:5230
ocfs2_mark_extent_written+0x1e3/0x2c0 fs/ocfs2/alloc.c:5276
ocfs2_dio_end_io_write+0x5bc/0xaa0 fs/ocfs2/aops.c:2350
ocfs2_dio_end_io+0x8c/0x180 fs/ocfs2/aops.c:2404
dio_complete+0x12e/0x4b0 fs/direct-io.c:281
__blockdev_direct_IO+0x1782/0x1b40 fs/direct-io.c:1303
ocfs2_direct_IO+0xf6/0x100 fs/ocfs2/aops.c:2441
generic_file_direct_write+0xb4/0x180 mm/filemap.c:4176
__generic_file_write_iter+0xa1/0x130 mm/filemap.c:4345
ocfs2_file_write_iter+0x68a/0x15a0 fs/ocfs2/file.c:2469

connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF


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