From: SJ Park <sj@kernel.org>
To: Karthikeyan KS <karthiproffesional@gmail.com>
Cc: SJ Park <sj@kernel.org>,
akpm@linux-foundation.org, damon@lists.linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/damon/sysfs: make next_update_jiffies per-kdamond
Date: Sat, 17 Oct 2026 09:01:42 -0700 [thread overview]
Message-ID: <20261017160143.102364-1-sj@kernel.org> (raw)
In-Reply-To: <20261017063152.994182-1-karthiproffesional@gmail.com>
Hi Karthikeyan,
On Sat, 17 Oct 2026 06:31:52 +0000 Karthikeyan KS <karthiproffesional@gmail.com> wrote:
> damon_sysfs_next_update_jiffies was a single static variable shared by
> all kdamonds, so with two or more kdamonds using refresh_ms their
> threads race on it in damon_sysfs_repeat_call_fn().
Thank you for this patch. However, I think the same issue is already fixed by
another patch [1]. Could you please check?
[1] https://lore.kernel.org/20260902002725.108635-5-sj@kernel.org
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-10-17 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 6:31 [PATCH] mm/damon/sysfs: make next_update_jiffies per-kdamond Karthikeyan KS
2026-10-17 16:01 ` SJ Park [this message]
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=20261017160143.102364-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=karthiproffesional@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