From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
Liew Rui Yan <aethernet65535@gmail.com>,
damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH v5 0/2] mm/damon: validate min_region_size to be power of 2
Date: Mon, 11 May 2026 20:36:29 -0700 [thread overview]
Message-ID: <20260512033630.39793-1-sj@kernel.org> (raw)
In-Reply-To: <20260501013750.71704-1-aethernet65535@gmail.com>
Hi Andrew,
On Fri, 1 May 2026 09:37:48 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> Problem
> =======
> When a user sets an invalid 'addr_unit' (e.g., 3) via DAMON_LRU_SORT or
> DAMON_RECLAIM, 'min_region_sz' becomes a non-power-of-2 value. While
> damon_commit_ctx() correctly detects this and returns -EINVAL, it sets
> the 'maybe_corrupted' flag during this process.
>
> This flag causes the running kdamond to terminate. While the termination
> is a safety measure, it is suboptimal in this case because the error is
> just a simple invalid input from the user, which shouldn't neccessitate
> stopping the kdamond.
>
> Solution
> ========
> Add an early validation in damon_lru_sort_apply_parameters() and
> damon_reclaim_apply_parameters() to check 'min_region_sz' before any
> state change occurs. If it is non-power-of-2, return -EINVAL immediately,
> preventing 'maybe_corrupted' from being set.
I think this series is good to go in my opinion. Could you please add this
series into mm.git?
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-05-12 3:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 1:37 [PATCH v5 0/2] mm/damon: validate min_region_size to be power of 2 Liew Rui Yan
2026-05-01 1:37 ` [PATCH v5 1/2] mm/damon/lru_sort: " Liew Rui Yan
2026-05-02 1:51 ` SeongJae Park
2026-05-01 1:37 ` [PATCH v5 2/2] mm/damon/reclaim: " Liew Rui Yan
2026-05-02 1:52 ` SeongJae Park
2026-05-12 3:36 ` SeongJae 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=20260512033630.39793-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aethernet65535@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--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