From: SeongJae Park <sj@kernel.org>
To: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
honggyu.kim@sk.com, damon@lists.linux.dev, linux-mm@kvack.org,
akpm@linux-foundation.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] mm/damon/core: set quota->charged_from to jiffies at first charge window
Date: Thu, 21 Aug 2025 10:53:06 -0700 [thread overview]
Message-ID: <20250821175307.82928-1-sj@kernel.org> (raw)
In-Reply-To: <20250821163346.1690784-1-ekffu200098@gmail.com>
On Fri, 22 Aug 2025 01:33:46 +0900 Sang-Heon Jeon <ekffu200098@gmail.com> wrote:
> Kernel initialize "jiffies" timer as 5 minutes below zero, as shown in
> include/linux/jiffies.h
>
> /*
> * Have the 32 bit jiffies value wrap 5 minutes after boot
> * so jiffies wrap bugs show up earlier.
> */
> #define INITIAL_JIFFIES ((unsigned long)(unsigned int) (-300*HZ))
>
> And jiffies comparison help functions cast unsigned value to signed to
> cover wraparound
>
> #define time_after_eq(a,b) \
> (typecheck(unsigned long, a) && \
> typecheck(unsigned long, b) && \
> ((long)((a) - (b)) >= 0))
>
> When quota->charged_from is initialized to 0, time_after_eq() can incorrectly
> return FALSE even after reset_interval has elapsed. This occurs when
> (jiffies - reset_interval) produces a value with MSB=1, which is interpreted
> as negative in signed arithmetic.
>
> This issue primarily affects 32-bit systems because:
> On 64-bit systems: MSB=1 values occur after ~292 million years from boot
> (assuming HZ=1000), almost impossible.
>
> On 32-bit systems: MSB=1 values occur during the first 5 minutes after boot,
> and the second half of every jiffies wraparound cycle, starting from day 25
> (assuming HZ=1000)
>
> When above unexpected FALSE return from time_after_eq() occurs, the
> charging window will not reset. The user impact depends on esz value
> at that time.
>
> If esz is 0, scheme ignores configured quotas and runs without any
> limits.
>
> If esz is not 0, scheme stops working once the quota is exhausted. It
> remains until the charging window finally resets.
>
> So, change quota->charged_from to jiffies at damos_adjust_quota() when
> it is considered as the first charge window. By this change, we can avoid
> unexpected FALSE return from time_after_eq()
Thank you for this patch, Sang-Heon! But, checkpatch.pl raises below three
warnings. Could you please fix those and send yet another version?
WARNING: Commit log lines starting with '#' are dropped by git as comments
#16:
#define INITIAL_JIFFIES ((unsigned long)(unsigned int) (-300*HZ))
WARNING: Commit log lines starting with '#' are dropped by git as comments
#21:
#define time_after_eq(a,b) \
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#26:
When quota->charged_from is initialized to 0, time_after_eq() can incorrectly
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-08-21 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 16:33 [PATCH v3] mm/damon/core: set quota->charged_from to jiffies at first charge window Sang-Heon Jeon
2025-08-21 17:53 ` SeongJae Park [this message]
2025-08-21 18:11 ` Sang-Heon Jeon
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=20250821175307.82928-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=ekffu200098@gmail.com \
--cc=honggyu.kim@sk.com \
--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;
as well as URLs for NNTP newsgroup(s).