From: Chao Yu <yuchao0@huawei.com>
To: Gao Xiang <hsiangkao@aol.com>, <linux-erofs@lists.ozlabs.org>
Cc: Chao Yu <chao@kernel.org>, Li Guifu <bluce.liguifu@huawei.com>,
Fang Wei <fangwei1@huawei.com>,
LKML <linux-kernel@vger.kernel.org>,
Gao Xiang <hsiangkao@redhat.com>,
Hongyu Jin <hongyu.jin@unisoc.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH v2] erofs: fix partially uninitialized misuse in z_erofs_onlinepage_fixup
Date: Wed, 24 Jun 2020 09:42:47 +0800 [thread overview]
Message-ID: <d9d2570a-ce51-79a7-6cc4-bd5e6f15cb4a@huawei.com> (raw)
In-Reply-To: <20200618234349.22553-1-hsiangkao@aol.com>
On 2020/6/19 7:43, Gao Xiang wrote:
> From: Gao Xiang <hsiangkao@redhat.com>
>
> Hongyu reported "id != index" in z_erofs_onlinepage_fixup() with
> specific aarch64 environment easily, which wasn't shown before.
>
> After digging into that, I found that high 32 bits of page->private
> was set to 0xaaaaaaaa rather than 0 (due to z_erofs_onlinepage_init
> behavior with specific compiler options). Actually we only use low
> 32 bits to keep the page information since page->private is only 4
> bytes on most 32-bit platforms. However z_erofs_onlinepage_fixup()
> uses the upper 32 bits by mistake.
>
> Let's fix it now.
>
> Reported-by: Hongyu Jin <hongyu.jin@unisoc.com>
> Fixes: 3883a79abd02 ("staging: erofs: introduce VLE decompression support")
> Cc: <stable@vger.kernel.org> # 4.19+
> Signed-off-by: Gao Xiang <hsiangkao@redhat.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
prev parent reply other threads:[~2020-06-24 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200618111936.19845-1-hsiangkao.ref@aol.com>
2020-06-18 11:19 ` [PATCH] " Gao Xiang
2020-06-18 23:43 ` [PATCH v2] " Gao Xiang
2020-06-19 9:00 ` 金红宇 (Hongyu Jin)
2020-06-19 9:13 ` 金红宇 (Hongyu Jin)
2020-06-24 1:42 ` 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=d9d2570a-ce51-79a7-6cc4-bd5e6f15cb4a@huawei.com \
--to=yuchao0@huawei.com \
--cc=bluce.liguifu@huawei.com \
--cc=chao@kernel.org \
--cc=fangwei1@huawei.com \
--cc=hongyu.jin@unisoc.com \
--cc=hsiangkao@aol.com \
--cc=hsiangkao@redhat.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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 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®