All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
	honggyu.kim@sk.com, damon@lists.linux.dev, linux-mm@kvack.org,
	stablee@vger.kernel.org
Subject: Re: [PATCH] mm/damon/core: fix damos_commit_filter not changing allow
Date: Fri, 15 Aug 2025 10:25:45 -0700	[thread overview]
Message-ID: <20250815172545.16704-1-sj@kernel.org> (raw)
In-Reply-To: <20250815094059.133769-1-ekffu200098@gmail.com>

On Fri, 15 Aug 2025 18:40:59 +0900 Sang-Heon Jeon <ekffu200098@gmail.com> wrote:

> Current damos_commit_filter() not persist allow value of filter. As a
> result, changing allow value of filter and commit doesn't change
> allow value.
> 
> Add the missing allow value update, so commit filter now persist changing
> allow value well.

Thank you for finding and fixing this!

> 
> Fixes: 9cb3d0b9dfce ("mm/damon/core: implement DAMON context commit function")

At the time of the commit, damos_filter->allow didn't exist.  I think below is
more correct.

Fixes: fe6d7fdd6249 ("mm/damon/core: add damos_filter->allow field")

Also,

Cc: stablee@vger.kernel.org # 6.14.x

> Signed-off-by: Sang-Heon Jeon <ekffu200098@gmail.com>
> ---
> While fixing kselftest, I found another bug and succeeded in
> reproducing. I think this patch is similar with previeous patch [1].
> Also instead of sending patch with test, should we check which is better:
> a seperate patch or patchset?

Separate patches are better for me.

I'm not sure how you will make the test, but I'd usggest making the test as a
kunit test.

Please refer to mm/damon/tets/core-kunit.h file.


Thanks,
SJ

[...]

  reply	other threads:[~2025-08-15 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15  9:40 [PATCH] mm/damon/core: fix damos_commit_filter not changing allow Sang-Heon Jeon
2025-08-15 17:25 ` SeongJae Park [this message]
2025-08-15 17:51   ` SeongJae Park
2025-08-16  1:18   ` Sang-Heon Jeon
2025-08-16 16:02     ` 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=20250815172545.16704-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=ekffu200098@gmail.com \
    --cc=honggyu.kim@sk.com \
    --cc=linux-mm@kvack.org \
    --cc=stablee@vger.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 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.