memory leak in ext4_multi_mount_protect

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    467f8165 Merge tag 'close-range-cloexec-unshare-v5.11' of ..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12b7fccb500000
kernel config:  https://syzkaller.appspot.com/x/.config?x=37c889fb8b2761af
dashboard link: https://syzkaller.appspot.com/bug?extid=d9e482e303930fa4f6ff
compiler:       gcc (GCC) 10.1.0-syz 20200507
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1230f8a7500000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d9e482e303930fa4f6ff@xxxxxxxxxxxxxxxxxxxxxxxxx

BUG: memory leak
unreferenced object 0xffff88812560f120 (size 32):
  comm "syz-executor.3", pid 11391, jiffies 4294966956 (age 10.520s)
  hex dump (first 32 bytes):
    28 2a e4 20 81 88 ff ff 00 f8 32 24 81 88 ff ff  (*. ......2$....
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<000000001fd6256c>] kmalloc include/linux/slab.h:552 [inline]
    [<000000001fd6256c>] ext4_multi_mount_protect+0x4a6/0x5d0 fs/ext4/mmp.c:367
    [<00000000ab3084f2>] ext4_fill_super+0x551e/0x5ac0 fs/ext4/super.c:4779
    [<00000000b7304a28>] mount_bdev+0x223/0x260 fs/super.c:1366
    [<00000000b580b323>] legacy_get_tree+0x2b/0x90 fs/fs_context.c:592
    [<000000005310f7d7>] vfs_get_tree+0x28/0x100 fs/super.c:1496
    [<000000006fc429ab>] do_new_mount fs/namespace.c:2875 [inline]
    [<000000006fc429ab>] path_mount+0xc5e/0x1170 fs/namespace.c:3205
    [<000000004f8c23d3>] do_mount fs/namespace.c:3218 [inline]
    [<000000004f8c23d3>] __do_sys_mount fs/namespace.c:3426 [inline]
    [<000000004f8c23d3>] __se_sys_mount fs/namespace.c:3403 [inline]
    [<000000004f8c23d3>] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3403
    [<000000002cff8f95>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
    [<00000000779cd3d5>] entry_SYSCALL_64_after_hwframe+0x44/0xa9



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