From: syzbot <syzbot+aa12d6106ea4ca1b6aae@syzkaller.appspotmail.com>
To: jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org, shaggy@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: memory leak in new_inode
Date: Fri, 20 Nov 2020 07:15:20 -0800 [thread overview]
Message-ID: <00000000000019465505b48b50d1@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: c2e7554e Merge tag 'gfs2-v5.10-rc4-fixes' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1362415a500000
kernel config: https://syzkaller.appspot.com/x/.config?x=dc8ee843c1fc6693
dashboard link: https://syzkaller.appspot.com/bug?extid=aa12d6106ea4ca1b6aae
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13a79ea6500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15b62d72500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+aa12d6106ea4ca1b6aae@syzkaller.appspotmail.com
executing program
executing program
BUG: memory leak
unreferenced object 0xffff88810ecc2a80 (size 1280):
comm "syz-executor002", pid 8495, jiffies 4294947195 (age 8.020s)
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 00 00 00 00 00 00 00 00 ................
backtrace:
[<00000000c920fbb4>] jfs_alloc_inode+0x18/0x60 fs/jfs/super.c:105
[<00000000c664943b>] alloc_inode+0x27/0x100 fs/inode.c:234
[<0000000072a6900b>] new_inode_pseudo fs/inode.c:930 [inline]
[<0000000072a6900b>] new_inode+0x23/0x100 fs/inode.c:959
[<0000000022579323>] diReadSpecial+0x28/0x1e0 fs/jfs/jfs_imap.c:424
[<0000000035d6f1c1>] jfs_mount+0xa7/0x280 fs/jfs/jfs_mount.c:107
[<00000000db4745f5>] jfs_fill_super+0x1ad/0x3a0 fs/jfs/super.c:562
[<00000000deb24c86>] mount_bdev+0x223/0x260 fs/super.c:1419
[<00000000355bbcf1>] legacy_get_tree+0x2b/0x90 fs/fs_context.c:592
[<00000000b4778640>] vfs_get_tree+0x28/0x100 fs/super.c:1549
[<00000000661148dd>] do_new_mount fs/namespace.c:2875 [inline]
[<00000000661148dd>] path_mount+0xc5e/0x1170 fs/namespace.c:3205
[<00000000184bf2c6>] do_mount fs/namespace.c:3218 [inline]
[<00000000184bf2c6>] __do_sys_mount fs/namespace.c:3426 [inline]
[<00000000184bf2c6>] __se_sys_mount fs/namespace.c:3403 [inline]
[<00000000184bf2c6>] __x64_sys_mount+0x18e/0x1d0 fs/namespace.c:3403
[<000000004af9fc85>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<000000004cba2559>] 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@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:[~2020-11-20 15:15 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=00000000000019465505b48b50d1@google.com \
--to=syzbot+aa12d6106ea4ca1b6aae@syzkaller.appspotmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®