From: syzbot <syzbot+d9e482e303930fa4f6ff@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, juan.carlos@b2bworthyleads.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] memory leak in ext4_multi_mount_protect
Date: Thu, 08 Apr 2021 22:43:19 -0700 [thread overview]
Message-ID: <00000000000027071505bf83a4f3@google.com> (raw)
In-Reply-To: <0000000000002c2f5b05b732ce65@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 4fa56ad0 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12390a96d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8dbd3c72fdc7777
dashboard link: https://syzkaller.appspot.com/bug?extid=d9e482e303930fa4f6ff
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=109aaa7ed00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e77d16d00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d9e482e303930fa4f6ff@syzkaller.appspotmail.com
executing program
BUG: memory leak
unreferenced object 0xffff888111edd780 (size 32):
comm "syz-executor633", pid 8448, jiffies 4294951405 (age 17.620s)
hex dump (first 32 bytes):
10 64 d1 0f 81 88 ff ff 00 10 7e 12 81 88 ff ff .d........~.....
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff81744606>] kmalloc include/linux/slab.h:554 [inline]
[<ffffffff81744606>] ext4_multi_mount_protect+0x4a6/0x5d0 fs/ext4/mmp.c:367
[<ffffffff81783614>] ext4_fill_super+0x56a4/0x5b20 fs/ext4/super.c:4769
[<ffffffff8154ebf3>] mount_bdev+0x223/0x260 fs/super.c:1367
[<ffffffff815aee7b>] legacy_get_tree+0x2b/0x90 fs/fs_context.c:592
[<ffffffff8154c7e8>] vfs_get_tree+0x28/0x100 fs/super.c:1497
[<ffffffff8158c8ee>] do_new_mount fs/namespace.c:2903 [inline]
[<ffffffff8158c8ee>] path_mount+0xc3e/0x1120 fs/namespace.c:3233
[<ffffffff8158d51e>] do_mount fs/namespace.c:3246 [inline]
[<ffffffff8158d51e>] __do_sys_mount fs/namespace.c:3454 [inline]
[<ffffffff8158d51e>] __se_sys_mount fs/namespace.c:3431 [inline]
[<ffffffff8158d51e>] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3431
[<ffffffff842ded2d>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<ffffffff84400068>] entry_SYSCALL_64_after_hwframe+0x44/0xae
prev parent reply other threads:[~2021-04-09 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 9:55 memory leak in ext4_multi_mount_protect syzbot
2021-04-09 5:43 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000027071505bf83a4f3@google.com \
--to=syzbot+d9e482e303930fa4f6ff@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=juan.carlos@b2bworthyleads.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).