From: Gao Xiang <xiang@kernel.org>
To: Yue Hu <zbestahu@163.com>
Cc: xiang@kernel.org, chao@kernel.org, linux-erofs@lists.ozlabs.org,
linux-kernel@vger.kernel.org, zhangwen@coolpad.com,
Yue Hu <huyue2@coolpad.com>
Subject: Re: [PATCH v2] erofs: fix invalid unmapped accesses in z_erofs_fill_inode_lazy()
Date: Sat, 8 Oct 2022 01:46:32 +0800 [thread overview]
Message-ID: <Y0Bl+G1uXaH2Au5N@debian> (raw)
In-Reply-To: <20221005013528.62977-1-zbestahu@163.com>
On Wed, Oct 05, 2022 at 09:35:28AM +0800, Yue Hu wrote:
> From: Yue Hu <huyue2@coolpad.com>
>
> Note that we are still accessing 'h_idata_size' and 'h_fragmentoff'
> after calling erofs_put_metabuf(), that is not correct. Fix it.
>
> Fixes: ab92184ff8f1 ("erofs: add on-disk compressed tail-packing inline support")
> Fixes: b15b2e307c3a ("erofs: support on-disk compressed fragments data")
> Signed-off-by: Yue Hu <huyue2@coolpad.com>
Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Thanks,
Gao Xiang
next prev parent reply other threads:[~2022-10-07 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 1:35 [PATCH v2] erofs: fix invalid unmapped accesses in z_erofs_fill_inode_lazy() Yue Hu
2022-10-07 17:46 ` Gao Xiang [this message]
2022-10-15 2:47 ` Chao Yu
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=Y0Bl+G1uXaH2Au5N@debian \
--to=xiang@kernel.org \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zbestahu@163.com \
--cc=zhangwen@coolpad.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