From: syzbot <syzbot+389b82b29093b3e2640a@syzkaller.appspotmail.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: akpm@linux-foundation.org, fmdefrancesco@gmail.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] memory leak in __get_metapage
Date: Wed, 05 Oct 2022 18:23:34 -0700 [thread overview]
Message-ID: <000000000000c4204105ea538a8a@google.com> (raw)
In-Reply-To: <2867034.e9J7NaK4W3@mypc>
> On Tuesday, October 4, 2022 10:49:42 AM CEST syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 4fe89d07dcc2 Linux 6.0
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=169a7924880000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=21254cf9c7c084e0
>> dashboard link: https://syzkaller.appspot.com/bug?extid=389b82b29093b3e2640a
>> 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=10bdd7ec880000
>>
>> Downloadable assets:
>> disk image: https://storage.googleapis.com/syzbot-assets/651a252f7035/
> disk-4fe89d07.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/776feb8e0e5b/
> vmlinux-4fe89d07.xz
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+389b82b29093b3e2640a@syzkaller.appspotmail.com
>>
>> BUG: memory leak
>> unreferenced object 0xffff888114339e80 (size 128):
>> comm "syz-executor.0", pid 3673, jiffies 4295017005 (age 12.610s)
>> hex dump (first 32 bytes):
>> 00 10 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:
>> [<ffffffff814927b3>] mempool_alloc+0x73/0x230 mm/mempool.c:392
>> [<ffffffff81c5aefa>] alloc_metapage fs/jfs/jfs_metapage.c:176 [inline]
>> [<ffffffff81c5aefa>] __get_metapage+0x38a/0x9b0 fs/jfs/jfs_metapage.c:651
>> [<ffffffff81c43862>] diNewExt+0x3f2/0x9d0 fs/jfs/jfs_imap.c:2265
>> [<ffffffff81c45254>] diAllocExt fs/jfs/jfs_imap.c:1945 [inline]
>> [<ffffffff81c45254>] diAllocAG+0x9a4/0xd50 fs/jfs/jfs_imap.c:1662
>> [<ffffffff81c4707f>] diAlloc+0x31f/0x900 fs/jfs/jfs_imap.c:1583
>> [<ffffffff81c57d9a>] ialloc+0x6a/0x3a0 fs/jfs/jfs_inode.c:56
>> [<ffffffff81c3a4c7>] jfs_mkdir+0xf7/0x480 fs/jfs/namei.c:225
>> [<ffffffff815fc703>] vfs_mkdir+0x223/0x340 fs/namei.c:4013
>> [<ffffffff816056e5>] do_mkdirat+0x1a5/0x1e0 fs/namei.c:4038
>> [<ffffffff81605859>] __do_sys_mkdir fs/namei.c:4058 [inline]
>> [<ffffffff81605859>] __se_sys_mkdir fs/namei.c:4056 [inline]
>> [<ffffffff81605859>] __x64_sys_mkdir+0x69/0x90 fs/namei.c:4056
>> [<ffffffff845eab95>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
>> [<ffffffff845eab95>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
>> [<ffffffff84800087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
>>
>> BUG: memory leak
>> unreferenced object 0xffff888114339e00 (size 128):
>> comm "syz-executor.0", pid 3673, jiffies 4295017005 (age 12.610s)
>> hex dump (first 32 bytes):
>> 00 10 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:
>> [<ffffffff814927b3>] mempool_alloc+0x73/0x230 mm/mempool.c:392
>> [<ffffffff81c5aefa>] alloc_metapage fs/jfs/jfs_metapage.c:176 [inline]
>> [<ffffffff81c5aefa>] __get_metapage+0x38a/0x9b0 fs/jfs/jfs_metapage.c:651
>> [<ffffffff81c43862>] diNewExt+0x3f2/0x9d0 fs/jfs/jfs_imap.c:2265
>> [<ffffffff81c45254>] diAllocExt fs/jfs/jfs_imap.c:1945 [inline]
>> [<ffffffff81c45254>] diAllocAG+0x9a4/0xd50 fs/jfs/jfs_imap.c:1662
>> [<ffffffff81c4707f>] diAlloc+0x31f/0x900 fs/jfs/jfs_imap.c:1583
>> [<ffffffff81c57d9a>] ialloc+0x6a/0x3a0 fs/jfs/jfs_inode.c:56
>> [<ffffffff81c3a4c7>] jfs_mkdir+0xf7/0x480 fs/jfs/namei.c:225
>> [<ffffffff815fc703>] vfs_mkdir+0x223/0x340 fs/namei.c:4013
>> [<ffffffff816056e5>] do_mkdirat+0x1a5/0x1e0 fs/namei.c:4038
>> [<ffffffff81605859>] __do_sys_mkdir fs/namei.c:4058 [inline]
>> [<ffffffff81605859>] __se_sys_mkdir fs/namei.c:4056 [inline]
>> [<ffffffff81605859>] __x64_sys_mkdir+0x69/0x90 fs/namei.c:4056
>> [<ffffffff845eab95>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
>> [<ffffffff845eab95>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
>> [<ffffffff84800087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
>>
>> BUG: memory leak
>> unreferenced object 0xffff888114339d80 (size 128):
>> comm "syz-executor.0", pid 3673, jiffies 4295017005 (age 12.610s)
>> hex dump (first 32 bytes):
>> 00 10 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:
>> [<ffffffff814927b3>] mempool_alloc+0x73/0x230 mm/mempool.c:392
>> [<ffffffff81c5aefa>] alloc_metapage fs/jfs/jfs_metapage.c:176 [inline]
>> [<ffffffff81c5aefa>] __get_metapage+0x38a/0x9b0 fs/jfs/jfs_metapage.c:651
>> [<ffffffff81c43862>] diNewExt+0x3f2/0x9d0 fs/jfs/jfs_imap.c:2265
>> [<ffffffff81c45254>] diAllocExt fs/jfs/jfs_imap.c:1945 [inline]
>> [<ffffffff81c45254>] diAllocAG+0x9a4/0xd50 fs/jfs/jfs_imap.c:1662
>> [<ffffffff81c4707f>] diAlloc+0x31f/0x900 fs/jfs/jfs_imap.c:1583
>> [<ffffffff81c57d9a>] ialloc+0x6a/0x3a0 fs/jfs/jfs_inode.c:56
>> [<ffffffff81c3a4c7>] jfs_mkdir+0xf7/0x480 fs/jfs/namei.c:225
>> [<ffffffff815fc703>] vfs_mkdir+0x223/0x340 fs/namei.c:4013
>> [<ffffffff816056e5>] do_mkdirat+0x1a5/0x1e0 fs/namei.c:4038
>> [<ffffffff81605859>] __do_sys_mkdir fs/namei.c:4058 [inline]
>> [<ffffffff81605859>] __se_sys_mkdir fs/namei.c:4056 [inline]
>> [<ffffffff81605859>] __x64_sys_mkdir+0x69/0x90 fs/namei.c:4056
>> [<ffffffff845eab95>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
>> [<ffffffff845eab95>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
>> [<ffffffff84800087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
>>
>> BUG: memory leak
>> unreferenced object 0xffff8881142f0300 (size 128):
>> comm "syz-executor.0", pid 3676, jiffies 4295017533 (age 7.330s)
>> hex dump (first 32 bytes):
>> 00 10 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:
>> [<ffffffff814927b3>] mempool_alloc+0x73/0x230 mm/mempool.c:392
>> [<ffffffff81c5aefa>] alloc_metapage fs/jfs/jfs_metapage.c:176 [inline]
>> [<ffffffff81c5aefa>] __get_metapage+0x38a/0x9b0 fs/jfs/jfs_metapage.c:651
>> [<ffffffff81c43862>] diNewExt+0x3f2/0x9d0 fs/jfs/jfs_imap.c:2265
>> [<ffffffff81c45254>] diAllocExt fs/jfs/jfs_imap.c:1945 [inline]
>> [<ffffffff81c45254>] diAllocAG+0x9a4/0xd50 fs/jfs/jfs_imap.c:1662
>> [<ffffffff81c4707f>] diAlloc+0x31f/0x900 fs/jfs/jfs_imap.c:1583
>> [<ffffffff81c57d9a>] ialloc+0x6a/0x3a0 fs/jfs/jfs_inode.c:56
>> [<ffffffff81c3a4c7>] jfs_mkdir+0xf7/0x480 fs/jfs/namei.c:225
>> [<ffffffff815fc703>] vfs_mkdir+0x223/0x340 fs/namei.c:4013
>> [<ffffffff816056e5>] do_mkdirat+0x1a5/0x1e0 fs/namei.c:4038
>> [<ffffffff81605859>] __do_sys_mkdir fs/namei.c:4058 [inline]
>> [<ffffffff81605859>] __se_sys_mkdir fs/namei.c:4056 [inline]
>> [<ffffffff81605859>] __x64_sys_mkdir+0x69/0x90 fs/namei.c:4056
>> [<ffffffff845eab95>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
>> [<ffffffff845eab95>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
>> [<ffffffff84800087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
>>
>
> #syz test git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
want 2 args (repo, branch), got 3
> Linux 6.0
>
>
>
>
next prev parent reply other threads:[~2022-10-06 1:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000008a5a2e05ea318aa9@google.com>
2022-10-04 8:52 ` [syzbot] memory leak in __get_metapage Dmitry Vyukov
2022-10-06 1:15 ` Fabio M. De Francesco
2022-10-06 1:16 ` syzbot
2022-10-11 11:00 ` syzbot
2022-10-06 1:20 ` Fabio M. De Francesco
2022-10-06 1:20 ` syzbot
2022-10-11 10:32 ` syzbot
2022-10-06 1:23 ` Fabio M. De Francesco
2022-10-06 1:23 ` syzbot [this message]
2022-10-11 10:32 ` syzbot
2022-10-06 1:28 ` Fabio M. De Francesco
2022-10-06 9:43 ` syzbot
2022-10-06 19:43 ` Fabio M. De Francesco
2022-10-06 22:03 ` syzbot
2022-10-06 23:26 ` Fabio M. De Francesco
2022-10-06 23:54 ` syzbot
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=000000000000c4204105ea538a8a@google.com \
--to=syzbot+389b82b29093b3e2640a@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=fmdefrancesco@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).