From: SJ Park <sj@kernel.org>
Cc: SJ Park <sj@kernel.org>,
stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Usama Arif <usamaarif642@gmail.com>,
Yueyang Pan <pyyjason@gmail.com>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [RFC PATCH v1.1 0/9] mm/damon: fix DAMOS bugs in core, paddr and vaddr
Date: Sun, 2 Aug 2026 09:26:21 -0700 [thread overview]
Message-ID: <20260802162631.90304-1-sj@kernel.org> (raw)
Fix misc bugs of DAMOS. Patch 1 make DAMOS less stress memory allocator
under extreme situation. Patch 2 fixes wrong DAMOS quota auto-tuning
feedback loop start point for PSI goal. Patches 3 and 4 fix wrong
folios walking in DAMON_PADDR. Patches 5 and 6 fix wrong folios walking
in DAMON_VADDR. Patches 7-9 handle extreme and unlikely memory
situations that can cause divide by zero and underflow.
All bugs are discovered by Sashiko.
The bugs are not very critical, but better to be merged sooner than
later. Since mm.git is closed for urgent changes, I aim for 7.3-rcX. I
will drop the RFC tag after 7.3-rc1.
Changes from RFC
- RFC: https://lore.kernel.org/20260801173554.94710-1-sj@kernel.org
- Use cached pte content (patch 5 and 6).
- Handle totalram < freeram case (patch 7).
- Fix wrong function name in commit message (patch 9).
SJ Park (9):
mm/damon/core: skip applying scheme if region split for quota fails
mm/damon/core: initialize damos_quota_goal->last_psi_total
mm/damon/paddr: respect folio end for DAMOS_STAT
mm/damon/paddr: respect folio end for DAMOS actions except STAT
mm/damon/vaddr: respect folio end for DAMOS_STAT
mm/damon/vaddr: respect folio end for DAMOS_MIGRATE_{HOT,COLD}
mm/damon/core: handle extreme memory state in damon_get_node_mem_bp()
mm/damon/core: handle extreme memory state in get_node_memcg_used_bp()
mm/damon/core: handle extreme memory state in get_in_active_mem_bp()
mm/damon/core.c | 37 +++++++++++++++++++++++++++++++------
mm/damon/paddr.c | 8 ++++----
mm/damon/vaddr.c | 10 ++++++++--
3 files changed, 43 insertions(+), 12 deletions(-)
base-commit: 481be0db7cfd092f0aea64e65ab0a9cacff88453
--
2.47.3
next reply other threads:[~2026-08-02 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 16:26 SJ Park [this message]
2026-08-02 16:26 ` [RFC PATCH v1.1 1/9] mm/damon/core: skip applying scheme if region split for quota fails SJ Park
2026-08-02 16:26 ` [RFC PATCH v1.1 2/9] mm/damon/core: initialize damos_quota_goal->last_psi_total SJ Park
2026-08-02 16:26 ` [RFC PATCH v1.1 3/9] mm/damon/paddr: respect folio end for DAMOS_STAT SJ Park
2026-08-02 16:26 ` [RFC PATCH v1.1 4/9] mm/damon/paddr: respect folio end for DAMOS actions except STAT SJ Park
2026-08-02 16:26 ` [RFC PATCH v1.1 5/9] mm/damon/vaddr: respect folio end for DAMOS_STAT SJ Park
2026-08-02 16:26 ` [RFC PATCH v1.1 6/9] mm/damon/vaddr: respect folio end for DAMOS_MIGRATE_{HOT,COLD} SJ Park
2026-08-02 16:26 ` [RFC PATCH v1.1 7/9] mm/damon/core: handle extreme memory state in damon_get_node_mem_bp() SJ Park
2026-08-02 16:26 ` [RFC PATCH v1.1 8/9] mm/damon/core: handle extreme memory state in get_node_memcg_used_bp() SJ Park
2026-08-02 16:26 ` [RFC PATCH v1.1 9/9] mm/damon/core: handle extreme memory state in get_in_active_mem_bp() 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=20260802162631.90304-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=pyyjason@gmail.com \
--cc=stable@vger.kernel.org \
--cc=usamaarif642@gmail.com \
/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