From: SeongJae Park <sj@kernel.org>
To: 최유호 <dbgh9129@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mm/damon/stat: roll back context on damon_call() failure
Date: Fri, 29 May 2026 09:00:29 -0700 [thread overview]
Message-ID: <20260529160030.85303-1-sj@kernel.org> (raw)
In-Reply-To: <CACrCO_XCxTDk7b8wo66CrxzfOXG50-uCxdE9tjJppH_ei5Wo+A@mail.gmail.com>
On Fri, 29 May 2026 11:17:01 -0400 최유호 <dbgh9129@gmail.com> wrote:
> Dear SJ
>
> On Fri, 29 May 2026 at 10:44, SeongJae Park <sj@kernel.org> wrote:
>
> > But, having one damon_ctx object in the memory is a real problem? Why?
>
> I agree that keeping one `damon_ctx` is unlikely to be a serious problem.
> My intention was not to address memory pressure but to maintain
> failure-path consistency. If initialization fails after the context is
> created and started, the internal state remains in place despite the
> operation returning an error. The cleanup is then deferred until a
> subsequent retry.
>
> For this reason, I think this is worth fixing as a correctness issue.
> That said, if you feel the current cleanup is sufficient, I can drop
> this patch.
Thank you for clarifying, Yuho. I think the current cleanup is ok, but I
understand it is confusing to read. Apparently that confused you at least, and
that's not ok. What about adding a comment explaining the context?
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-05-29 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 3:15 [PATCH v1] mm/damon/stat: roll back context on damon_call() failure Yuho Choi
2026-05-29 14:44 ` SeongJae Park
2026-05-29 15:17 ` 최유호
2026-05-29 16:00 ` SeongJae Park [this message]
2026-05-29 20:29 ` 최유호
2026-05-29 23:40 ` 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=20260529160030.85303-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=dbgh9129@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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