From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"# 5 . 16 . x" <stable@vger.kernel.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/damon/core: handle zero intervals in damon_max_nr_accesses()
Date: Sun, 21 Jun 2026 11:03:47 -0700 [thread overview]
Message-ID: <20260621180348.92118-1-sj@kernel.org> (raw)
In-Reply-To: <20260621154808.86431-1-sj@kernel.org>
On Sun, 21 Jun 2026 08:48:06 -0700 SeongJae Park <sj@kernel.org> wrote:
> damon_max_nr_accesses() causes a divide-by-zero if the sampling interval
> is set to zero by the user. If the aggregation interval is set to zero,
> the function returns zero. It is wrong, since the real maximum
> nr_acceses in the setup should be one. Worse yet, it can cause another
> divide-by-zero from its caller, damon_hot_score(), since it uses
> damon_max_nr_accesses() return value as a denominator.
>
> Fix the problem by setting the denominator in the function as 1 when the
> sampling interval is zero. Also ensure the return value is always 1 or
> greater.
>
> The issue was discovered [1] by Sashiko.
>
> [1] https://lore.kernel.org/20260619202459.145010-1-sj@kernel.org
>
> Fixes: 198f0f4c58b9 ("mm/damon/vaddr,paddr: support pageout prioritization")
Sashiko found [1] another bug that was introduced by another commit. I will
repost this patch with a fix for the another bug.
[1] https://lore.kernel.org/20260621175849.91990-1-sj@kernel.org
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-06-21 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 15:48 [PATCH] mm/damon/core: handle zero intervals in damon_max_nr_accesses() SeongJae Park
2026-06-21 18:03 ` SeongJae 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=20260621180348.92118-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 \
--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