From: Chao Yu <chao@kernel.org>
To: Chen Zhongjin <chenzhongjin@huawei.com>,
huyue2@coolpad.com,
syzbot+6f8cd9a0155b366d227f@syzkaller.appspotmail.com,
linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
xiang@kernel.org, jefflexu@linux.alibaba.com
Subject: Re: [PATCH -next v3] erofs: Fix pcluster memleak when its block address is zero
Date: Tue, 6 Dec 2022 23:07:07 +0800 [thread overview]
Message-ID: <1022b823-b0a7-0afa-bb88-954182e372cf@kernel.org> (raw)
In-Reply-To: <Y42Kz6sVkf+XqJRB@debian>
On 2022/12/5 14:08, Gao Xiang wrote:
> Hi all,
>
> On Mon, Dec 05, 2022 at 11:49:57AM +0800, Chen Zhongjin wrote:
>> syzkaller reported a memleak:
>> https://syzkaller.appspot.com/bug?id=62f37ff612f0021641eda5b17f056f1668aa9aed
>>
>> unreferenced object 0xffff88811009c7f8 (size 136):
>> ...
>> backtrace:
>> [<ffffffff821db19b>] z_erofs_do_read_page+0x99b/0x1740
>> [<ffffffff821dee9e>] z_erofs_readahead+0x24e/0x580
>> [<ffffffff814bc0d6>] read_pages+0x86/0x3d0
>> ...
>>
>> syzkaller constructed a case: in z_erofs_register_pcluster(),
>> ztailpacking = false and map->m_pa = zero. This makes pcl->obj.index be
>> zero although pcl is not a inline pcluster.
>>
>> Then following path adds refcount for grp, but the refcount won't be put
>> because pcl is inline.
>>
>> z_erofs_readahead()
>> z_erofs_do_read_page() # for another page
>> z_erofs_collector_begin()
>> erofs_find_workgroup()
>> erofs_workgroup_get()
>>
>> Since it's illegal for the block address of a pcluster to be zero, add
>> check here to avoid registering the pcluster which would be leaked.
>>
>> Fixes: cecf864d3d76 ("erofs: support inline data decompression")
>> Reported-by: syzbot+6f8cd9a0155b366d227f@syzkaller.appspotmail.com
>> Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com>
>> ---
>> v1 -> v2:
>> As Gao's advice, we should fail to register pcluster if m_pa is zero.
>> Maked it this way and changed the commit message.
>>
>> v2 -> v3:
>> Slightly fix commit message and add -next tag.
>
> I've updated the patch itself as below
> (Since we only need to fail out for non-tailpacking cases, tailpacking
> inline inodes could still have m_pa < EROFS_BLKSIZ):
>
> From f5e037e760d338ca0c116e507be663cb843d42f0 Mon Sep 17 00:00:00 2001
> From: Chen Zhongjin <chenzhongjin@huawei.com>
> Date: Mon, 5 Dec 2022 11:49:57 +0800
> Subject: [PATCH] erofs: Fix pcluster memleak when its block address is zero
>
> syzkaller reported a memleak:
> https://syzkaller.appspot.com/bug?id=62f37ff612f0021641eda5b17f056f1668aa9aed
>
> unreferenced object 0xffff88811009c7f8 (size 136):
> ...
> backtrace:
> [<ffffffff821db19b>] z_erofs_do_read_page+0x99b/0x1740
> [<ffffffff821dee9e>] z_erofs_readahead+0x24e/0x580
> [<ffffffff814bc0d6>] read_pages+0x86/0x3d0
> ...
>
> syzkaller constructed a case: in z_erofs_register_pcluster(),
> ztailpacking = false and map->m_pa = zero. This makes pcl->obj.index be
> zero although pcl is not a inline pcluster.
>
> Then following path adds refcount for grp, but the refcount won't be put
> because pcl is inline.
>
> z_erofs_readahead()
> z_erofs_do_read_page() # for another page
> z_erofs_collector_begin()
> erofs_find_workgroup()
> erofs_workgroup_get()
>
> Since it's illegal for the block address of a non-inlined pcluster to
> be zero, add check here to avoid registering the pcluster which would
> be leaked.
>
> Fixes: cecf864d3d76 ("erofs: support inline data decompression")
> Reported-by: syzbot+6f8cd9a0155b366d227f@syzkaller.appspotmail.com
> Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com>
> Reviewed-by: Yue Hu <huyue2@coolpad.com>
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2022-12-06 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 3:49 [PATCH -next v3] erofs: Fix pcluster memleak when its block address is zero Chen Zhongjin via Linux-erofs
2022-12-05 3:49 ` Chen Zhongjin
2022-12-05 4:38 ` Gao Xiang
2022-12-05 4:38 ` Gao Xiang
2022-12-05 5:41 ` Yue Hu
2022-12-05 6:08 ` Gao Xiang
2022-12-05 6:08 ` Gao Xiang
2022-12-06 15:07 ` Chao Yu [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=1022b823-b0a7-0afa-bb88-954182e372cf@kernel.org \
--to=chao@kernel.org \
--cc=chenzhongjin@huawei.com \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+6f8cd9a0155b366d227f@syzkaller.appspotmail.com \
--cc=xiang@kernel.org \
/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.