From: SJ Park <sj@kernel.org>
Cc: SJ Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [RFC PATCH 0/4] mm/damon: allow NULL or unstarted damon_ctx parameter for damon_call()
Date: Wed, 12 Aug 2026 20:49:55 -0700 [thread overview]
Message-ID: <20260813035001.97364-1-sj@kernel.org> (raw)
Callers of damon_call() should validate the damon_ctx object parameter.
If it is NULL or never damon_start()-ed object, damon_call() could
dereference the NULL pointer or indefinitely hang. Ensuring all callers
doing the validation correctly has turned out to be difficult. Handle
the corner cases inside the core layer and remove callers' validations.
Patches 1 and 2 respectively allow passing NULL and not yet
damon_start()-ed ctx parameter to damon_call(). Patches 3 and 4 remove
the callers side validations in DMON_RECLAIM and DASMON_LRU_SORT,
respectively.
SJ Park (4):
mm/damon/core: handle NULL ctx parameter in damon_call()
mm/damon/core: set ctx->call_controls_obsolete in damon_new_ctx()
mm/damon/reclaim: remove unnecessary damon_call() param validation
mm/damon/lru_sort: remove unnecessary damon_call() param validation
mm/damon/core.c | 7 +++----
mm/damon/lru_sort.c | 8 --------
mm/damon/reclaim.c | 8 --------
3 files changed, 3 insertions(+), 20 deletions(-)
base-commit: c8520e181a2aaf85290d0447656de0df112dbbea
--
2.47.3
next reply other threads:[~2026-08-13 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 3:49 SJ Park [this message]
2026-08-13 3:49 ` [RFC PATCH 1/4] mm/damon/core: handle NULL ctx parameter in damon_call() SJ Park
2026-08-13 3:49 ` [RFC PATCH 2/4] mm/damon/core: set ctx->call_controls_obsolete in damon_new_ctx() SJ Park
2026-08-13 3:49 ` [RFC PATCH 3/4] mm/damon/reclaim: remove unnecessary damon_call() param validation SJ Park
2026-08-13 3:49 ` [RFC PATCH 4/4] mm/damon/lru_sort: " SJ 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=20260813035001.97364-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--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