From: SJ Park <sj@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: SJ Park <sj@kernel.org>,
stable@vger.kernel.org, damon@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 6.18.y] mm/damon/sysfs: read ops_id only once in damon_sysfs_apply_inputs()
Date: Wed, 9 Sep 2026 17:45:03 -0700 [thread overview]
Message-ID: <20260910004504.118187-1-sj@kernel.org> (raw)
In-Reply-To: <2026090945-spookily-leotard-ecf3@gregkh>
On Wed, 9 Sep 2026 15:01:49 +0200 Greg KH <greg@kroah.com> wrote:
> On Tue, Sep 08, 2026 at 08:28:30PM -0700, SJ Park wrote:
> > damon_sysfs_apply_inputs() reads ops_id twice. It could race with
> > ops_id_store(). As a result, the min_region_sz could wrongly be set up.
> > Read it once.
> >
> > The user impact is trivial. Sane users ain't update the parameter in
> > parallel. Even if it happens, the DAMON core layer handles the wrong
> > min_region_sz (!is_power_of_2()). Even if somehow the race ended up
> > making a min_region_sz that is different from the user's intention but
> > still valid, only monitoring itself runs differently than expected. No
> > critical consequences like kernel panic or memory corruption happen
> >
> > The issue was discovered [1] by Sashiko.
> >
> > Link: https://lore.kernel.org/20260715031002.108504-7-sj@kernel.org
> > Link: https://lore.kernel.org/20260703172417.95426-1-sj@kernel.org [1]
> > Fixes: 8d009da32f13 ("mm/damon/sysfs: set damon_ctx->min_sz_region only for paddr use case")
> > Signed-off-by: SJ Park <sj@kernel.org>
> > Cc: <stable@vger.kernel.org> # 6.18.x
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > (cherry picked from commit 5adaaa28be8a79ddd7e103b171f9d6e14e7fc26e)
> > Signed-off-by: SJ Park <sj@kernel.org>
> > ---
> > mm/damon/sysfs.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/mm/damon/sysfs.c b/mm/damon/sysfs.c
> > index a6c3e83a3dad5..655e4de69bee8 100644
> > --- a/mm/damon/sysfs.c
> > +++ b/mm/damon/sysfs.c
> > @@ -1432,14 +1432,16 @@ static inline bool damon_sysfs_kdamond_running(
> > static int damon_sysfs_apply_inputs(struct damon_ctx *ctx,
> > struct damon_sysfs_context *sys_ctx)
> > {
> > + enum damon_ops_id ops_id;
> > int err;
> >
> > - err = damon_select_ops(ctx, sys_ctx->ops_id);
> > + ops_id = READ_ONCE(sys_ctx->ops_id);
> > + err = damon_select_ops(ctx, ops_id);
> > if (err)
> > return err;
> > ctx->addr_unit = sys_ctx->addr_unit;
> > /* addr_unit is respected by only DAMON_OPS_PADDR */
> > - if (sys_ctx->ops_id == DAMON_OPS_PADDR)
> > + if (ops_id == DAMON_OPS_PADDR)
> > ctx->min_sz_region = max(
> > DAMON_MIN_REGION / sys_ctx->addr_unit, 1);
> > err = damon_sysfs_set_attrs(ctx, sys_ctx->attrs);
> > --
> > 2.47.3
> >
> >
>
> Does not apply :(
Seems a patch in 6.18.50..6.18.51-rc1 is causing the conflict. I just rebased
the patch on 6.18.51-rc1 and posted as another reply [1].
[1] https://lore.kernel.org/20260910004154.115973-1-sj@kernel.org
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-09-10 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026090858-arousal-getting-ee35@gregkh>
2026-09-09 3:28 ` [PATCH 6.18.y] mm/damon/sysfs: read ops_id only once in damon_sysfs_apply_inputs() SJ Park
2026-09-09 3:45 ` sashiko-bot
2026-09-09 13:01 ` Greg KH
2026-09-10 0:45 ` SJ Park [this message]
2026-09-10 0:41 ` SJ Park
2026-09-11 11:20 ` Sasha Levin
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=20260910004504.118187-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=greg@kroah.com \
--cc=stable@vger.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