From: SeongJae Park <sj@kernel.org>
To: JaeJoon Jung <rgbi3307@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
damon@lists.linux.dev, linux-mm@kvack.org, rgbi3307@nate.com
Subject: Re: [PATCH] mm/damon/core: modified control->repeat loop at the kdamond_call()
Date: Wed, 31 Dec 2025 07:29:29 -0800 [thread overview]
Message-ID: <20251231152931.82221-1-sj@kernel.org> (raw)
In-Reply-To: <CAHOvCC6RwVzujJcuosiignDEQoe038eRJHuJVLEtJ4-qP8Ot9w@mail.gmail.com>
On Wed, 31 Dec 2025 15:23:49 +0900 JaeJoon Jung <rgbi3307@gmail.com> wrote:
> On Wed, 31 Dec 2025 at 10:28, SeongJae Park <sj@kernel.org> wrote:
> >
> > On Mon, 29 Dec 2025 16:57:15 -0800 SeongJae Park <sj@kernel.org> wrote:
> >
> > > On Tue, 30 Dec 2025 09:14:37 +0900 JaeJoon Jung <rgbi3307@gmail.com> wrote:
> > >
> > > > I will reflect the above in patch v2.
> > > > Would you like me to resend patch v2 ?
> > >
> > > I just found my fix [1] of the bug that you reported has a race condition. And
> > > to fix that, I think kdamond_call() will anyway need to be modified. I will
> > > shortly send more details as a reply to the fix [1]. Can you please hold this
> > > refactoring until all discussions about the bug fix is done? Sorry for your
> > > inconvenience.
> > >
> > > [1] https://lore.kernel.org/20251228183105.289441-1-sj@kernel.org
> >
> > I ended up sending the new version of the fix [1] without changes on
> > kdamond_call(). Unless you have concerns on the fix, please feel free to
> > proceed to v2 of this patch. Thank you for patiently waiting.
> >
> > [1] https://lore.kernel.org/20251231012315.75835-1-sj@kernel.org
>
> My patch for the kdamond_call() function further improves control->list
> to behave as a FIFO. This also improves stability against the control->list
> collision issue encountered when damon_call() is called.
> If there are no further objections, I'll send you Patch v2.
If you want to say something about damon_call() uaf issue, let's make a
conclusion about it first, rather than mixing topics.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-12-31 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 12:43 [PATCH] mm/damon/core: modified control->repeat loop at the kdamond_call() JaeJoon Jung
2025-12-25 1:07 ` SeongJae Park
2025-12-25 3:10 ` JaeJoon Jung
2025-12-25 20:00 ` SeongJae Park
2025-12-26 2:19 ` JaeJoon Jung
2025-12-26 18:31 ` SeongJae Park
2025-12-26 23:42 ` JaeJoon Jung
2025-12-30 0:14 ` JaeJoon Jung
2025-12-30 0:57 ` SeongJae Park
2025-12-31 1:28 ` SeongJae Park
2025-12-31 6:23 ` JaeJoon Jung
2025-12-31 15:29 ` SeongJae Park [this message]
2026-01-01 1:22 ` JaeJoon Jung
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=20251231152931.82221-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=rgbi3307@gmail.com \
--cc=rgbi3307@nate.com \
/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.