From: sashiko-bot@kernel.org
To: "SeongJae Park" <sj@kernel.org>
Cc: damon@lists.linux.dev
Subject: Re: [PATCH 6.6.y] mm/damon/reclaim: detect and use fresh enabled and kdamond_pid values
Date: Thu, 14 May 2026 02:05:06 +0000 [thread overview]
Message-ID: <20260514020506.D1DB7C19425@smtp.kernel.org> (raw)
In-Reply-To: <20260513045858.204442-1-sj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Calls to undeclared and undefined functions `damon_is_running()` and `damon_kdamond_pid()` will cause a build failure.
--
commit f496e53eab697919d0061167b54870a26d15920a
Author: SeongJae Park <sj@kernel.org>
mm/damon/reclaim: detect and use fresh enabled and kdamond_pid values
This commit modifies DAMON_RECLAIM to query the running status and kdamond PID
dynamically to avoid stale parameters.
Link: https://lore.kernel.org/20260419161003.79176-1-sj@kernel.org
Link: https://lore.kernel.org/20260419161003.79176-2-sj@kernel.org
> diff --git a/mm/damon/reclaim.c b/mm/damon/reclaim.c
> index 586daa2cefe4f..e264f202714eb 100644
> --- a/mm/damon/reclaim.c
> +++ b/mm/damon/reclaim.c
[ ... ]
> @@ -203,60 +194,93 @@ static int damon_reclaim_turn(bool on)
[ ... ]
> +static bool damon_reclaim_enabled(void)
> +{
> + if (!ctx)
> + return false;
> + return damon_is_running(ctx);
Will this cause a build failure? It appears damon_is_running() isn't declared
in include/linux/damon.h or defined anywhere in the tree.
> +}
[ ... ]
> +static int damon_reclaim_kdamond_pid_load(char *buffer,
> + const struct kernel_param *kp)
> +{
> + int kdamond_pid = -1;
> +
> + if (ctx) {
> + kdamond_pid = damon_kdamond_pid(ctx);
Will this also fail to compile? Similar to above, damon_kdamond_pid() doesn't
seem to be defined. Is this missing a dependency or an incomplete backport?
> + if (kdamond_pid < 0)
> + kdamond_pid = -1;
> + }
> + return sprintf(buffer, "%d\n", kdamond_pid);
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260513045858.204442-1-sj@kernel.org?part=1
next prev parent reply other threads:[~2026-05-14 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 14:05 FAILED: patch "[PATCH] mm/damon/reclaim: detect and use fresh enabled and" failed to apply to 6.6-stable tree gregkh
2026-05-13 4:58 ` [PATCH 6.6.y] mm/damon/reclaim: detect and use fresh enabled and kdamond_pid values SeongJae Park
2026-05-14 2:05 ` sashiko-bot [this message]
2026-05-14 5:36 ` 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=20260514020506.D1DB7C19425@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sj@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.