From: syzbot <syzbot+193c375dcddb4f345091@syzkaller.appspotmail.com>
To: anna.schumaker@netapp.com, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org, syzkaller-bugs@googlegroups.com,
trond.myklebust@hammerspace.com
Subject: memory leak in nfs_fs_context_parse_monolithic
Date: Fri, 14 Feb 2020 09:37:14 -0800 [thread overview]
Message-ID: <000000000000fe87be059e8ca7bc@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 0bf999f9 linux/pipe_fs_i.h: fix kernel-doc warnings after ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1589bd4ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2802e33434f4f863
dashboard link: https://syzkaller.appspot.com/bug?extid=193c375dcddb4f345091
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13dec65ee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c05311e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+193c375dcddb4f345091@syzkaller.appspotmail.com
executing program
BUG: memory leak
unreferenced object 0xffff8881166b3ac0 (size 32):
comm "syz-executor191", pid 7127, jiffies 4294946216 (age 12.850s)
hex dump (first 32 bytes):
00 66 73 00 00 00 00 00 00 00 00 00 00 00 00 00 .fs.............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<000000006202a794>] kmemleak_alloc_recursive include/linux/kmemleak.h:43 [inline]
[<000000006202a794>] slab_post_alloc_hook mm/slab.h:586 [inline]
[<000000006202a794>] slab_alloc mm/slab.c:3320 [inline]
[<000000006202a794>] __do_kmalloc mm/slab.c:3654 [inline]
[<000000006202a794>] __kmalloc_track_caller+0x165/0x300 mm/slab.c:3671
[<000000007e324303>] kstrdup+0x3a/0x70 mm/util.c:60
[<000000002835aac3>] nfs23_parse_monolithic fs/nfs/fs_context.c:958 [inline]
[<000000002835aac3>] nfs_fs_context_parse_monolithic+0x5cf/0x8f0 fs/nfs/fs_context.c:1147
[<000000004fe3f934>] parse_monolithic_mount_data+0x37/0x40 fs/fs_context.c:679
[<00000000dccb779f>] do_new_mount fs/namespace.c:2818 [inline]
[<00000000dccb779f>] do_mount+0x945/0xc80 fs/namespace.c:3107
[<000000006234487e>] __do_sys_mount fs/namespace.c:3316 [inline]
[<000000006234487e>] __se_sys_mount fs/namespace.c:3293 [inline]
[<000000006234487e>] __x64_sys_mount+0xc0/0x140 fs/namespace.c:3293
[<00000000d2937fdd>] do_syscall_64+0x73/0x220 arch/x86/entry/common.c:294
[<00000000fa6ba8f3>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2020-02-14 17:37 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=000000000000fe87be059e8ca7bc@google.com \
--to=syzbot+193c375dcddb4f345091@syzkaller.appspotmail.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trond.myklebust@hammerspace.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.