From: Chao Yu via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] erofs: fix potential return value overflow of z_erofs_shrink_scan()
Date: Thu, 16 Jan 2025 16:31:56 +0800 [thread overview]
Message-ID: <11ffcd03-c3ce-4d2b-8360-1968092f72c1@kernel.org> (raw)
In-Reply-To: <20250114040058.459981-1-hsiangkao@linux.alibaba.com>
On 1/14/25 12:00, Gao Xiang wrote:
> z_erofs_shrink_scan() could return small numbers due to the mistyped
> `freed`.
>
> Although I don't think it has any visible impact.
Agreed, it's an extreme case...
>
> Fixes: 3883a79abd02 ("staging: erofs: introduce VLE decompression support")
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: chao@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] erofs: fix potential return value overflow of z_erofs_shrink_scan()
Date: Thu, 16 Jan 2025 16:31:56 +0800 [thread overview]
Message-ID: <11ffcd03-c3ce-4d2b-8360-1968092f72c1@kernel.org> (raw)
In-Reply-To: <20250114040058.459981-1-hsiangkao@linux.alibaba.com>
On 1/14/25 12:00, Gao Xiang wrote:
> z_erofs_shrink_scan() could return small numbers due to the mistyped
> `freed`.
>
> Although I don't think it has any visible impact.
Agreed, it's an extreme case...
>
> Fixes: 3883a79abd02 ("staging: erofs: introduce VLE decompression support")
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-01-16 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 4:00 [PATCH] erofs: fix potential return value overflow of z_erofs_shrink_scan() Gao Xiang
2025-01-14 4:00 ` Gao Xiang
2025-01-16 8:31 ` Chao Yu via Linux-erofs [this message]
2025-01-16 8:31 ` Chao Yu
2025-01-16 8:33 ` 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=11ffcd03-c3ce-4d2b-8360-1968092f72c1@kernel.org \
--to=linux-erofs@lists.ozlabs.org \
--cc=chao@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-kernel@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 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.