[syzbot] [reiserfs?] memory leak in reiserfs_parse_options (2)

[syzbot] [reiserfs?] memory leak in reiserfs_parse_options (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    a689b938df39 Merge tag 'block-2023-01-06' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14e229c2480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5ddca4921a53cff2
dashboard link: https://syzkaller.appspot.com/bug?extid=67d4d8261283b46b21ac
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15adc3fc480000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=150b3bcc480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a368fc04c846/disk-a689b938.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b6771146e261/vmlinux-a689b938.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ac22fc91deb9/bzImage-a689b938.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/15583b49f0c4/mount_0.gz

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

BUG: memory leak
unreferenced object 0xffff88810f4f5600 (size 32):
  comm "syz-executor300", pid 5077, jiffies 4294958926 (age 8.040s)
  hex dump (first 32 bytes):
    73 79 7a 00 00 00 00 00 00 00 00 00 00 00 00 00  syz.............
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<ffffffff814f9c67>] __do_kmalloc_node mm/slab_common.c:967 [inline]
    [<ffffffff814f9c67>] __kmalloc_node_track_caller+0x47/0x120 mm/slab_common.c:988
    [<ffffffff814e9feb>] kstrdup+0x3b/0x70 mm/util.c:61
    [<ffffffff8177b635>] reiserfs_parse_options+0xad5/0x1090 fs/reiserfs/super.c:1279
    [<ffffffff8177f73d>] reiserfs_fill_super+0x17d/0x15d0 fs/reiserfs/super.c:1933
    [<ffffffff8160f503>] mount_bdev+0x223/0x260 fs/super.c:1359
    [<ffffffff81673a1b>] legacy_get_tree+0x2b/0x90 fs/fs_context.c:610
    [<ffffffff8160d088>] vfs_get_tree+0x28/0x100 fs/super.c:1489
    [<ffffffff81650f27>] do_new_mount fs/namespace.c:3145 [inline]
    [<ffffffff81650f27>] path_mount+0xc37/0x10d0 fs/namespace.c:3475
    [<ffffffff81651b5e>] do_mount fs/namespace.c:3488 [inline]
    [<ffffffff81651b5e>] __do_sys_mount fs/namespace.c:3697 [inline]
    [<ffffffff81651b5e>] __se_sys_mount fs/namespace.c:3674 [inline]
    [<ffffffff81651b5e>] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3674
    [<ffffffff848ef725>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
    [<ffffffff848ef725>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
    [<ffffffff84a00087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd



---
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@googlegroups.com.

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