From: SJ Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SJ Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [PATCH 6.18.y] mm/damon/core: do non-safe region walk on kdamond_apply_schemes()
Date: Sat, 3 Oct 2026 10:59:32 -0700 [thread overview]
Message-ID: <20261003175933.34727-1-sj@kernel.org> (raw)
In-Reply-To: <20261003175623.7F2081F0089B@smtp.kernel.org>
On Sat, 03 Oct 2026 17:56:23 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
> - [High] mm: damon: state leak in damos_skip_charged_region() on split failure
> - [High] mm: damon: double processing of regions due to dynamic iteration
I will fix the state leak. The second one is a minor bug that also exist in
mainline, so no blocker of this patch in my opinion. Please read my previous
reply [1] for more details.
[1] https://lore.kernel.org/20261003165326.32932-1-sj@kernel.org
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-10-03 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 16:31 [PATCH 6.18.y] mm/damon/core: do non-safe region walk on kdamond_apply_schemes() SJ Park
2026-10-03 16:53 ` (sashiko review) " SJ Park
2026-10-03 17:56 ` sashiko-bot
2026-10-03 17:59 ` SJ Park [this message]
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=20261003175933.34727-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-bot@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