From: "Xu Xin (vivo)" <xu.xin@linux.dev>
To: david@kernel.org
Cc: akpm@linux-foundation.org, chengming.zhou@linux.dev,
donettom@linux.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, stable@vger.kernel.org, xu.xin@linux.dev
Subject: [PATCH v2 0/3] mm/ksm: fix ksm_zero_pages accounting on fork
Date: Fri, 20 Nov 2026 15:42:30 +0800 [thread overview]
Message-ID: <20261120074230.40269-1-xu.xin@linux.dev> (raw)
Currently, fork() wrongly inherits the parent's ksm_zero_pages counter
and keeps the KSM dirty-bit marker on zero-page PTEs, inflating both the
child's per-mm counter and the global ksm_zero_pages counter.
Patch 1 fixes this by resetting the child's mm->ksm_zero_pages to 0 in
ksm_fork() and clearing the KSM zero-page marker when copying present
PTEs, and documents the behavior.
Patch 2 fixes a false-positive bug in the existing KSM fork selftest by
removing a redundant init_global_file_handles() call in the child.
Patch 3 extends the selftest to verify that ksm_zero_pages is not
inherited across fork().
---
Changes in v2:
- Encapsulate zero-page PTE marker clearing into a dedicated
might_clear_ksm_zero_pte() helper and simplify the code comment. (David)
- Fix compilation error by adding stub implementation of
might_clear_ksm_zero_pte() for !CONFIG_KSM. (kernel test robot)
- Document the fork() interaction and MADV_UNMERGEABLE behavior for
ksm_zero_pages in Documentation/admin-guide/mm/ksm.rst. (David)
- Fix a false-positive bug in the KSM fork selftest (patch 2/3) and
extend it to verify ksm_zero_pages is not inherited on fork (patch 3/3).
Xu Xin (vivo) (3):
mm/ksm: do not inherit ksm_zero_pages counter or PTE markers on fork
selftests/mm: fix false-positive KSM fork test by dropping
init_global_file_handles()
selftests/mm: verify ksm_zero_pages is not inherited on fork
Documentation/admin-guide/mm/ksm.rst | 7 +++-
include/linux/ksm.h | 18 ++++++++--
mm/memory.c | 2 ++
.../selftests/mm/ksm_functional_tests.c | 35 ++++++++++++++-----
4 files changed, 49 insertions(+), 13 deletions(-)
--
2.34.1
next reply other threads:[~2026-11-20 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 7:42 Xu Xin (vivo) [this message]
2026-11-20 7:43 ` [PATCH v2 1/3] mm/ksm: do not inherit ksm_zero_pages counter or PTE markers on fork Xu Xin (vivo)
2026-11-20 7:44 ` [PATCH v2 2/3] selftests/mm: fix false-positive KSM fork test by dropping init_global_file_handles() Xu Xin (vivo)
2026-11-20 7:44 ` [PATCH v2 3/3] selftests/mm: verify ksm_zero_pages is not inherited on fork Xu Xin (vivo)
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=20261120074230.40269-1-xu.xin@linux.dev \
--to=xu.xin@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=david@kernel.org \
--cc=donettom@linux.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.