From: Yue Hu <zbestahu@gmail.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, huyue2@coolpad.com
Subject: Re: [PATCH] erofs: fix wrong kunmap when using LZMA on HIGHMEM platforms
Date: Mon, 6 Mar 2023 16:18:08 +0800 [thread overview]
Message-ID: <20230306161808.000046c0.zbestahu@gmail.com> (raw)
In-Reply-To: <20230305134455.88236-1-hsiangkao@linux.alibaba.com>
On Sun, 5 Mar 2023 21:44:55 +0800
Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
> As the call trace shown, the root cause is kunmap incorrect pages:
>
> BUG: kernel NULL pointer dereference, address: 00000000
> CPU: 1 PID: 40 Comm: kworker/u5:0 Not tainted 6.2.0-rc5 #4
> Workqueue: erofs_worker z_erofs_decompressqueue_work
> EIP: z_erofs_lzma_decompress+0x34b/0x8ac
> z_erofs_decompress+0x12/0x14
> z_erofs_decompress_queue+0x7e7/0xb1c
> z_erofs_decompressqueue_work+0x32/0x60
> process_one_work+0x24b/0x4d8
> ? process_one_work+0x1a4/0x4d8
> worker_thread+0x14c/0x3fc
> kthread+0xe6/0x10c
> ? rescuer_thread+0x358/0x358
> ? kthread_complete_and_exit+0x18/0x18
> ret_from_fork+0x1c/0x28
> ---[ end trace 0000000000000000 ]---
>
> The bug is trivial and should be fixed now. It has no impact on
> !HIGHMEM platforms.
>
> Fixes: 622ceaddb764 ("erofs: lzma compression support")
> Cc: <stable@vger.kernel.org> # 5.16+
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Yue Hu <huyue2@coolpad.com>
> ---
> fs/erofs/decompressor_lzma.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/erofs/decompressor_lzma.c b/fs/erofs/decompressor_lzma.c
> index 091fd5adf818..5cd612a8f858 100644
> --- a/fs/erofs/decompressor_lzma.c
> +++ b/fs/erofs/decompressor_lzma.c
> @@ -278,7 +278,7 @@ int z_erofs_lzma_decompress(struct z_erofs_decompress_req *rq,
> }
> }
> if (no < nrpages_out && strm->buf.out)
> - kunmap(rq->in[no]);
> + kunmap(rq->out[no]);
> if (ni < nrpages_in)
> kunmap(rq->in[ni]);
> /* 4. push back LZMA stream context to the global list */
next prev parent reply other threads:[~2023-03-06 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 13:44 [PATCH] erofs: fix wrong kunmap when using LZMA on HIGHMEM platforms Gao Xiang
2023-03-06 8:18 ` Yue Hu [this message]
2023-03-09 14:28 ` 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=20230306161808.000046c0.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=huyue2@coolpad.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