From: SJ Park <sj@kernel.org>
To: Liew Rui Yan <aethernet65535@gmail.com>
Cc: SJ Park <sj@kernel.org>,
sashiko-bot@kernel.org, damon@lists.linux.dev,
sashiko-reviews@lists.linux.dev
Subject: Re: [PATCH] mm/damon/tests/core-kunit: add test for unconditionally skipping the last region
Date: Mon, 31 Aug 2026 17:25:14 -0700 [thread overview]
Message-ID: <20260901002515.88585-1-sj@kernel.org> (raw)
In-Reply-To: <20260831122842.9091-1-aethernet65535@gmail.com>
On Mon, 31 Aug 2026 20:28:15 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> On Mon, 31 Aug 2026 11:50:14 +0000 sashiko-bot@kernel.org wrote:
[...]
> > [Severity: Medium]
> > Does this patch omit the fix for the core logic?
> >
> > Without an accompanying fix for damos_skip_charged_region() in
> > mm/damon/core.c, won't this new test unconditionally fail and break CI?
> >
> > Because the underlying bug is not fixed in this patch, the old logic still
> > triggers and returns true when it processes the last region:
> >
> > mm/damon/core.c:damos_skip_charged_region() {
> > ...
> > if (quota->charge_target_from) {
> > if (t != quota->charge_target_from)
> > return true;
> > if (r == damon_last_region(t)) {
> > quota->charge_target_from = NULL;
> > quota->charge_addr_from = 0;
> > return true;
> > }
> > ...
> > }
>
> This test is add for [1]. Therefore, this patch can only be merged
> after [1] is merged.
Makes sense.
>
> [1] https://lore.kernel.org/damon/20260830063159.6347-1-aethernet65535@gmail.com
I wonder if you are open to repost this after the dependent patch is merged
into mm-new. It would be definitely inconvenient for you, but that would help
us getting AI review help. What do you think?
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-09-01 0:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 11:37 [PATCH] mm/damon/tests/core-kunit: add test for unconditionally skipping the last region Liew Rui Yan
2026-08-31 11:50 ` sashiko-bot
2026-08-31 12:28 ` Liew Rui Yan
2026-09-01 0:25 ` SJ Park [this message]
2026-09-01 0:55 ` Liew Rui Yan
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=20260901002515.88585-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aethernet65535@gmail.com \
--cc=damon@lists.linux.dev \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.