From: SeongJae Park <sj@kernel.org>
To: Liew Rui Yan <aethernet65535@gmail.com>
Cc: SeongJae Park <sj@kernel.org>, damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH] mm/damon: validate addr_unit to be power of 2
Date: Sat, 28 Mar 2026 06:29:37 -0700 [thread overview]
Message-ID: <20260328132937.9580-1-sj@kernel.org> (raw)
In-Reply-To: <20260328022651.41744-1-aethernet65535@gmail.com>
On Sat, 28 Mar 2026 10:26:51 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
[...]
> Just to make sure I captured the full context, in my earlier follow-ups
> [1][2] (in case they got folded in your email client):
>
> - Does the current kdamond termination on invalid user input align with
> your design goal mentioned in [3] (stopping only for "internal
> errors")?
No. I still think it would be better to avoid wrong input-caused termination.
But in a simple way. Also, it would be better to be consistent.
>
> - Would a lightweight fix be acceptable? For example, performing
> validation at the very beginning of damon_commit_ctx(), and returning
> -EINVAL before setting 'maybe_corrupted' to true. Since no
> modifications to 'dst' would have occurred, kdamond could safely
> continue with its old configuration.
I suggested you to try something similar to what DAMON_SYSFS is doing. But I
didn't get your response to the idea yet. Could you please let me know what do
you think about the approach?
>
> Thank you again for your time, and guidance. :>
You're welcome.
>
> [1] https://lore.kernel.org/20260327064517.68131-1-aethernet65535@gmail.com
> [2] https://lore.kernel.org/20260327121009.38374-1-aethernet65535@gmail.com
> [3] https://lore.kernel.org/20260319151528.86490-1-sj@kernel.org
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-03-28 13:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 6:26 [PATCH] mm/damon: validate addr_unit to be power of 2 Liew Rui Yan
2026-03-27 6:45 ` Liew Rui Yan
2026-03-27 12:10 ` Liew Rui Yan
2026-03-27 8:11 ` (sashiko review) " Liew Rui Yan
2026-03-27 8:27 ` Liew Rui Yan
2026-03-27 14:14 ` SeongJae Park
2026-03-27 14:56 ` Liew Rui Yan
2026-03-28 0:14 ` SeongJae Park
2026-03-28 2:26 ` Liew Rui Yan
2026-03-28 13:29 ` SeongJae Park [this message]
2026-03-28 14:13 ` SeongJae Park
2026-03-28 17:44 ` Liew Rui Yan
2026-03-28 18:06 ` SeongJae Park
2026-03-28 18:43 ` Liew Rui Yan
2026-03-29 3:20 ` SeongJae Park
2026-03-29 7:51 ` Liew Rui Yan
2026-03-29 15:15 ` SeongJae Park
2026-03-30 6:08 ` Liew Rui Yan
2026-03-30 7:17 ` Liew Rui Yan
2026-03-30 23:34 ` SeongJae Park
2026-03-30 23:33 ` 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=20260328132937.9580-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aethernet65535@gmail.com \
--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 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.