From: syzbot <syzbot+9d67170b20e8f94351c8@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
nathan@kernel.org, ndesaulniers@google.com,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
trix@redhat.com
Subject: [syzbot] memory leak in ntfs_init_fs_context
Date: Mon, 22 Aug 2022 23:18:35 -0700 [thread overview]
Message-ID: <000000000000cb172905e6e28808@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 1c23f9e627a7 Linux 6.0-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16caa92d080000
kernel config: https://syzkaller.appspot.com/x/.config?x=b1831d905b683446
dashboard link: https://syzkaller.appspot.com/bug?extid=9d67170b20e8f94351c8
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=161472f3080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=145f3e2d080000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9d67170b20e8f94351c8@syzkaller.appspotmail.com
executing program
executing program
BUG: memory leak
unreferenced object 0xffff8881100918a0 (size 32):
comm "syz-executor151", pid 3611, jiffies 4294944949 (age 8.110s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 c0 ff c0 ff 00 00 00 00 ................
backtrace:
[<ffffffff81b23cb2>] kmalloc include/linux/slab.h:600 [inline]
[<ffffffff81b23cb2>] kzalloc include/linux/slab.h:733 [inline]
[<ffffffff81b23cb2>] ntfs_init_fs_context+0x22/0x1e0 fs/ntfs3/super.c:1397
[<ffffffff81650025>] alloc_fs_context+0x225/0x3b0 fs/fs_context.c:290
[<ffffffff8162beb3>] do_new_mount fs/namespace.c:3025 [inline]
[<ffffffff8162beb3>] path_mount+0x6f3/0x10d0 fs/namespace.c:3370
[<ffffffff8162cfde>] do_mount fs/namespace.c:3383 [inline]
[<ffffffff8162cfde>] __do_sys_mount fs/namespace.c:3591 [inline]
[<ffffffff8162cfde>] __se_sys_mount fs/namespace.c:3568 [inline]
[<ffffffff8162cfde>] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3568
[<ffffffff845e4855>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff845e4855>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
[<ffffffff84800087>] 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
reply other threads:[~2022-08-23 6:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000cb172905e6e28808@google.com \
--to=syzbot+9d67170b20e8f94351c8@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.com \
/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