From: Liew Rui Yan <aethernet65535@gmail.com>
To: sj@kernel.org
Cc: aethernet65535@gmail.com, damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH v3 1/2] mm/damon/lru_sort: validate min_region_size to be power of 2
Date: Sat, 4 Apr 2026 17:11:22 +0800 [thread overview]
Message-ID: <20260404091122.6255-1-aethernet65535@gmail.com> (raw)
In-Reply-To: <20260403161906.65008-1-sj@kernel.org>
Hi SeongJae,
On Fri, 3 Apr 2026 09:19:06 -0700 SeongJae Park <sj@kernel.org> wrote:
> As Quanmin also asked, clarifying the unexpected termination would be nice.
I will clarify "unexpected termination" in v4's commit message:
"Unexpectedly" here means the kdamond terminates without the user
requesting it (e.g., not by wrtting "N" to 'enabled').
> I remember I suggested adding stable@, but only if you think it deserve. I'm
> now not very sure if this deserves Cc-ing stable@. As I mentioned before,
I think this deserves Cc stable@ because:
- The issue can be triggered by accidental user misconfiguration
- It causes kdamond termination and hard to recover/restart. Once
triggered, kdamond remains in an unusable state, and I have not found
a way to recover/restart it through the sysfs interface without a
system reboot.
- The fix is small and low-risk
- It improves user experience on stable kernels
But I'm open to dropping it if you think otherwise.
> there are multiple patches to review in parallel (you are also having such
> multiple patches in the queue). Please don't expect I will follow full
> contexts especially when a single person posting multiple patches in parallel
> every day or two, and bear in mind with me.
>
> Sorry about the limited bandwidth from my side. You could also simply slow
> down your pace, though.
I will try to adjust my pace. I've also noticed that the quality of my
recent replies/patches hasn't been ideal, and I will try to be less
rushed in the future. Thank you for your understanding and suggestion.
> For stable@ Cc-ing patches, more clearly describing the user impact would be
> nice, and helpful for judging if it deserves that. Could you please elaborate?
I will add a "User Impact" section in v4's commit message:
User Impact
===========
Currently, if a user commit an invalid 'addr_unit', kdamond may
terminate abruptly. Once terminated, it cannot be easily restarted
via sysfs, pontentially requiring a system reboot to restore DAMON
functionality. This patch prevent such termination by validating
parameters (addr_unit and min_region_sz) early.
Best regards,
Rui Yan
next prev parent reply other threads:[~2026-04-04 9:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 5:23 [PATCH v3 0/2] mm/damon: validate min_region_size to be power of 2 Liew Rui Yan
2026-04-03 5:23 ` [PATCH v3 1/2] mm/damon/lru_sort: " Liew Rui Yan
2026-04-03 8:31 ` (sashiko review) " Liew Rui Yan
2026-04-03 15:55 ` SeongJae Park
2026-04-04 9:09 ` Liew Rui Yan
2026-04-04 20:18 ` SeongJae Park
2026-04-03 8:59 ` Quanmin Yan
2026-04-03 9:50 ` Liew Rui Yan
2026-04-03 16:19 ` SeongJae Park
2026-04-04 9:11 ` Liew Rui Yan [this message]
2026-04-04 20:30 ` SeongJae Park
2026-04-06 9:41 ` Liew Rui Yan
2026-04-06 15:50 ` SeongJae Park
2026-04-03 5:23 ` [PATCH v3 2/2] mm/damon/reclaim: " Liew Rui Yan
2026-04-03 8:33 ` (sashiko review) " Liew Rui Yan
2026-04-03 16:07 ` SeongJae Park
2026-04-03 16:20 ` 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=20260404091122.6255-1-aethernet65535@gmail.com \
--to=aethernet65535@gmail.com \
--cc=damon@lists.linux.dev \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox