From: SeongJae Park <sj@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] mm/damon/sysfs: eliminate potential uninitialized variable warning
Date: Mon, 6 Nov 2023 06:41:37 -0800 [thread overview]
Message-ID: <20231106144137.9772-1-sj@kernel.org> (raw)
In-Reply-To: <739e6aaf-a634-4e33-98a8-16546379ec9f@moroto.mountain>
Hi Dan,
On Mon, 6 Nov 2023 17:07:40 +0300 Dan Carpenter <dan.carpenter@linaro.org> wrote:
> The "err" variable is not initialized if damon_target_has_pid(ctx) is
> false and sys_target->regions->nr is zero.
Thank you for fixing this. I actually noticed this issue from Coverity Weekly
Scan of -next tree (CID 1570878), and was about to send very same fix, but you
were faster :)
>
> Fixes: 0bcd216c4741 ("mm/damon/sysfs: update monitoring target regions for online input commit")
Cc stable?
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
Reviewed-by: SeongJae Park <sj@kernel.org>
Thanks,
SJ
> ---
> mm/damon/sysfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/damon/sysfs.c b/mm/damon/sysfs.c
> index e27846708b5a..1dfa96d4de99 100644
> --- a/mm/damon/sysfs.c
> +++ b/mm/damon/sysfs.c
> @@ -1172,7 +1172,7 @@ static int damon_sysfs_update_target(struct damon_target *target,
> struct damon_ctx *ctx,
> struct damon_sysfs_target *sys_target)
> {
> - int err;
> + int err = 0;
>
> if (damon_target_has_pid(ctx)) {
> err = damon_sysfs_update_target_pid(target, sys_target->pid);
> --
> 2.42.0
>
next prev parent reply other threads:[~2023-11-06 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 14:07 [PATCH] mm/damon/sysfs: eliminate potential uninitialized variable warning Dan Carpenter
2023-11-06 14:41 ` SeongJae Park [this message]
2023-11-06 16:23 ` Dan Carpenter
2023-11-06 16:52 ` SeongJae Park
2023-11-07 3:54 ` Dan Carpenter
2023-11-06 19:05 ` Deepak R Varma
2023-11-06 20:49 ` SeongJae Park
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=20231106144137.9772-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=dan.carpenter@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).