From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Junrui Luo <moonafterrain@outlook.com>
Cc: Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org>,
Yue Hu <zbestahu@gmail.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>,
Sandeep Dhavale <dhavale@google.com>,
Hongbo Li <lihongbo22@huawei.com>,
Chunhai Guo <guochunhai@vivo.com>,
"linux-erofs@lists.ozlabs.org" <linux-erofs@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yuhao Jiang <danisjiang@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] erofs: fix unsigned underflow in z_erofs_lz4_handle_overlap()
Date: Thu, 9 Apr 2026 18:56:42 +0800 [thread overview]
Message-ID: <f608d440-6d26-4dd9-b838-b5ad1e70541c@linux.alibaba.com> (raw)
In-Reply-To: <3F909329-EB34-4B5E-A26D-081D9031DE01@outlook.com>
On 2026/4/9 18:38, Junrui Luo wrote:
> Hi Gao Xiang,
>
> Thank you for the review.
>
> On Thu, Apr 09, 2026 at 03:28:21PM +0800, Gao Xiang wrote:
>
>> For this kind of stuff, do you have a reproducer?
>
> I constructed a crafted EROFS image declaring plen=8192 and i_size=4096, giving
> inpages=2 and outpages=1. Tested under QEMU with kernel (v7.0-rc6) plus a temporary
> pr_warn trace in z_erofs_lz4_handle_overlap():
>
> [ 12.889652] erofs: BOUNDARY CHECK: outpages=1 < inpages=2
>
> The image mounts and the decompressor is reached with
> partial_decoding=false and outpages < inpages.
>
>> I'm not sure what you're saying, but I don't think
>> you really understand the entire logic.
>>
>> `m_la + m_llen` should not be page-aligned for typical
>> erofs images, you can just mkfs.erofs -zlz4hc with some
>> file and check it yourself.
>>
>> BTW, I just check upstream, and the inplace branch
>> works prefectly.
>
> During testing I observed that the inplace branch was not entered with
> my crafted image and incorrectly concluded it was structurally unreachable.
> I apologize for the incorrect analysis.
Can you share your initial crafted image binary
with `gzip -9 | base64` encoding here?
I think the proper place to fix this is in
z_erofs_map_sanity_check().
But we only accept patches with proper reproducible
ways (e.g. base64-encoded zipped images or syzbot
link).
Thanks,
Gao Xiang
next prev parent reply other threads:[~2026-04-09 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 6:57 Junrui Luo
2026-04-09 7:28 ` Gao Xiang
2026-04-09 10:38 ` Junrui Luo
2026-04-09 10:56 ` Gao Xiang [this message]
2026-04-09 11:49 ` Junrui Luo
2026-04-09 12:14 ` Gao Xiang
2026-04-09 13:22 ` Gao Xiang
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=f608d440-6d26-4dd9-b838-b5ad1e70541c@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=danisjiang@gmail.com \
--cc=dhavale@google.com \
--cc=guochunhai@vivo.com \
--cc=jefflexu@linux.alibaba.com \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moonafterrain@outlook.com \
--cc=stable@vger.kernel.org \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.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®