From: SJ Park <sj@kernel.org>
To: sashiko-bot@kernel.org
Cc: SJ Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: [RFC PATCH 3/8] mm/damon/sysfs: remove duplicated commit input validity check
Date: Wed, 1 Jul 2026 17:09:25 -0700 [thread overview]
Message-ID: <20260702000925.86443-1-sj@kernel.org> (raw)
In-Reply-To: <20260701152903.DD8D51F000E9@smtp.kernel.org>
On Wed, 01 Jul 2026 15:29:02 +0000 sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [High] Removing the explicit `test_ctx` parameter validation in `damon_sysfs_commit_input` exposes an underlying flaw in `damon_commit_ctx`, allowing invalid sysfs inputs to corrupt the running context and terminate the background kdamond thread.
> --
>
> Note: Due to system limitations regarding exact code recitation, this report
> uses a free-form summary of the issue rather than inline patch quoting.
>
> commit bec0828fbe945683bcef8cfdb56247414f2510d8
> Author: SJ Park <sj@kernel.org>
> Subject: mm/damon/sysfs: remove duplicated commit input validity check
>
> This commit removes the explicit test_ctx validation inside
> damon_sysfs_commit_input(), assuming the same validation logic is safely
> embedded inside damon_commit_ctx().
>
> [Severity: High]
> Does removing the sysfs-level test_ctx wrapper expose the running context to
> corruption from invalid user inputs?
>
> In mm/damon/core.c:damon_commit_ctx(), it appears the underlying validation
> logic tests 'dst' against the temporary 'test_ctx' instead of testing the
> new 'src' parameters:
>
> damon_commit_ctx()
> err = __damon_commit_ctx(test_ctx, dst);
> if (err)
> goto out;
> err = __damon_commit_ctx(dst, src);
>
> Because damon_sysfs_commit_input() now relies entirely on damon_commit_ctx()
> for validation, what happens if invalid configuration parameters (such as a
> min_region_sz that is not a power of 2) are passed via the sysfs interface?
>
> It looks like __damon_commit_ctx(dst, src) will fail halfway through, returning
> -EINVAL but leaving the running context with maybe_corrupted = true. Can this
> cause the background kdamond_fn thread to silently abort without recovering,
> effectively resulting in a denial of service for the monitoring session?
Correct. I will fix damon_commit_ctx() side validation in the next revision.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-07-02 0:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 14:48 [RFC PATCH 0/8] mm/damon: validate all parameters in the core SJ Park
2026-07-01 14:48 ` [RFC PATCH 1/8] mm/damon/core: safely validate src on damon_commit_ctx() SJ Park
2026-07-01 15:01 ` sashiko-bot
2026-07-01 15:06 ` SJ Park
2026-07-01 14:48 ` [RFC PATCH 2/8] mm/damon/core: do parameter testing commit on damon_start() SJ Park
2026-07-01 15:20 ` sashiko-bot
2026-07-02 0:05 ` SJ Park
2026-07-01 14:48 ` [RFC PATCH 3/8] mm/damon/sysfs: remove duplicated commit input validity check SJ Park
2026-07-01 15:29 ` sashiko-bot
2026-07-02 0:09 ` SJ Park [this message]
2026-07-01 14:48 ` [RFC PATCH 4/8] mm/damon/reclaim: remove duplicated min_region_sz power of 2 check SJ Park
2026-07-01 15:42 ` sashiko-bot
2026-07-02 0:10 ` SJ Park
2026-07-01 14:48 ` [RFC PATCH 5/8] mm/damon/lru_sort: remove duplicated min_region_sz power_of_2() check SJ Park
2026-07-01 15:56 ` sashiko-bot
2026-07-02 0:15 ` SJ Park
2026-07-01 14:48 ` [RFC PATCH 6/8] mm/damon: document region size validation in damon_set_regions() SJ Park
2026-07-01 16:04 ` sashiko-bot
2026-07-02 0:16 ` SJ Park
2026-07-01 14:48 ` [RFC PATCH 7/8] mm/damon/core: remove start, end check in damon_set_region_system_rams() SJ Park
2026-07-01 16:22 ` sashiko-bot
2026-07-02 0:18 ` SJ Park
2026-07-01 14:48 ` [RFC PATCH 8/8] mm/damon/sysfs: remove region size validation SJ Park
2026-07-01 16:34 ` sashiko-bot
2026-07-02 0:19 ` 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=20260702000925.86443-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=sashiko-bot@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