public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
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] mm/damon: validate addr_unit to be power of 2
Date: Mon, 30 Mar 2026 14:08:51 +0800	[thread overview]
Message-ID: <20260330060851.4659-1-aethernet65535@gmail.com> (raw)
In-Reply-To: <20260329151507.44171-1-sj@kernel.org>

Hi SeongJae,

On Sun, 29 Mar 2026 08:15:07 -0700 SeongJae Park <sj@kernel.org> wrote:

> On Sun, 29 Mar 2026 15:51:07 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> [...]
> > To confirm, are you suggesting something like the first approach [1]?
> > 
> >     if (input_addr_unit < PAGE_SIZE && !is_power_of_2(input_addr_unit))
> >         return -EINVAL;
> 
> Yes.  But the real constraint is min_region_sz, so testing it would be more
> simple and effective.  E.g.,
> 
> 	if (!is_power_of_2(param_ctx->min_region_sz))
> 		return -EINVAL;
> > 
> > [1] https://lore.kernel.org/20260325071709.9699-1-aethernet65535@gmail.com

Thank you for the example.

The 'param_ctx' you mentioned confused me for a moment, as it doesn't
exist in the current addr_unit_store(). But I assume you are suggesting
that we should validate the result of 'min_region_sz' rather than the
'addr_unit' itself, and this check should happen within the
addr_unit_store() callback.

So, would something like this in addr_uint_store() be what you expect?

    if (!input_addr_unit)
        return -EINVAL;

    min_region_sz = max(PAGE_SIZE / input_addr_unit, 1);
    if (!is_power_of_2(min_region_sz))
        return -EINVAL;

This keeps the fix local to the modules, and directly enforces the
power-of-2 constraint on the actual monitoring granularity.

Best regards,
Rui Yan


  reply	other threads:[~2026-03-30  6:08 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
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 [this message]
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=20260330060851.4659-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