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: Sat, 16 Aug 2025 09:02:51 -0700 [thread overview]
Message-ID: <20250816160251.63436-1-sj@kernel.org> (raw)
In-Reply-To: <CABFDxMG2Mr+zO6i7a2_J5S5j7+4etiQYFur=0a+U3oNOS8TMMA@mail.gmail.com>
On Sat, 16 Aug 2025 10:18:13 +0900 Sang-Heon Jeon <ekffu200098@gmail.com> wrote:
> Hi SeongJae
>
> On Sat, Aug 16, 2025 at 2:25 AM SeongJae Park <sj@kernel.org> wrote:
> >
> > 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")
>
> I found a wrong commit, I'll fix them.
>
> > Also,
> >
> > Cc: stablee@vger.kernel.org # 6.14.x
>
> I'll also add them.
>
> > > 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.
>
> I made kselftest with drgn, but I think that kunit could be a solution as well.
Thank you :) I prefer kunit here, since the test should be for the specific
core function that can easily be tested using kunit. Writing it as a drgn
based selftest seems too much to me.
> Honestly, I haven't used kunit test before, so i need to look into of
> that. Please just wait a little bit.
No worry, take your time and fun :)
FYI, you can run DAMON kunit test as below:
$ ./tools/testing/kunit/kunit.py run --kunitconfig ./mm/damon/tests
And the document is available at
https://docs.kernel.org/dev-tools/kunit/index.html
Thanks,
SJ
[...]
prev parent reply other threads:[~2025-08-16 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 9:40 Sang-Heon Jeon
2025-08-15 17:25 ` SeongJae Park
2025-08-15 17:51 ` SeongJae Park
2025-08-16 1:18 ` Sang-Heon Jeon
2025-08-16 16:02 ` 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=20250816160251.63436-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox