From: SeongJae Park <sj@kernel.org>
To: JaeJoon Jung <rgbi3307@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
Asier Gutierrez <gutierrez.asier@huawei-partners.com>,
akpm@linux-foundation.org, damon@lists.linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
wangkefeng.wang@huawei.com, artem.kuzin@huawei.com,
stepanov.anatoly@huawei.com
Subject: Re: [RFC PATCH v1] mm: improve call_controls_lock
Date: Thu, 1 Jan 2026 14:44:19 -0800 [thread overview]
Message-ID: <20260101224420.73826-1-sj@kernel.org> (raw)
In-Reply-To: <CAHOvCC5Frn16MiaP7AjzvJNPfnGXyjcWmhtwNnKQzXwz3VUL9w@mail.gmail.com>
On Thu, 1 Jan 2026 11:34:13 +0900 JaeJoon Jung <rgbi3307@gmail.com> wrote:
[...]
> I'm sorry, but this conversation has gotten so long that I'm getting lost.
> I've given my opinion, so I hope you understand.
Unfortunately I'm still not fully undertanding your opinions. But I understand
that I'm asking details about your opinions, more than what you can answer at
the moment with your available time. It is unfortunate, but I think asking you
more qeustions will only stress you, so I'd like to accept this as a
communication failure and simply forget your mails you sent so far regarding
the fix of damon_call() uaf issue.
That said, I believe you made huge amount of effort in spite of your limited
resources. And your report of the damon_call() uaf issue was really helpful.
I truely do appreciate your effort.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-01-01 22:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 14:55 Asier Gutierrez
2025-12-29 15:22 ` SeongJae Park
2025-12-30 9:02 ` Gutierrez Asier
2025-12-31 5:01 ` SeongJae Park
2025-12-31 2:15 ` JaeJoon Jung
2025-12-31 4:59 ` SeongJae Park
2025-12-31 6:10 ` JaeJoon Jung
2025-12-31 7:51 ` JaeJoon Jung
2025-12-31 15:32 ` SeongJae Park
2026-01-01 1:11 ` JaeJoon Jung
2026-01-01 2:00 ` SeongJae Park
2026-01-01 2:34 ` JaeJoon Jung
2026-01-01 22:44 ` SeongJae Park [this message]
2026-01-01 1:07 ` JaeJoon Jung
2026-01-01 1:51 ` SeongJae Park
2026-01-01 2:29 ` 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=20260101224420.73826-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=artem.kuzin@huawei.com \
--cc=damon@lists.linux.dev \
--cc=gutierrez.asier@huawei-partners.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rgbi3307@gmail.com \
--cc=stepanov.anatoly@huawei.com \
--cc=wangkefeng.wang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox