From: Andrew Morton <akpm@linux-foundation.org>
To: Itamar-Dalal <dalalitamar@gmail.com>
Cc: linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, david@redhat.com,
lorenzo.stoakes@oracle.com, riel@surriel.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, harry.yoo@oracle.com,
jannh@google.com, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, shuah@kernel.org
Subject: Re: [PATCH] Add a new test 'migrate.cow_after_fork' that verifies correct RMAP handling of Copy-On-Write pages after fork(). Before a write, parent and child share the same PFN; after a write, the child’s PFN differs, confirming proper COW duplication.
Date: Tue, 14 Oct 2025 14:29:57 -0700 [thread overview]
Message-ID: <20251014142957.4253f2fc62e9e49bfc4433ab@linux-foundation.org> (raw)
In-Reply-To: <20251014194944.20341-1-dalalitamar@gmail.com>
On Tue, 14 Oct 2025 22:49:44 +0300 Itamar-Dalal <dalalitamar@gmail.com> wrote:
> Subject: [PATCH] Add a new test 'migrate.cow_after_fork' that verifies correct RMAP handling of Copy-On-Write pages after fork(). Before a write, parent and child share the same PFN; after a write, the child’s PFN differs, confirming proper COW duplication.
> Date: Tue, 14 Oct 2025 22:49:44 +0300
> X-Mailer: git-send-email 2.34.1
>
> Signed-off-by: Itamar-Dalal <dalalitamar@gmail.com>
> ---
> tools/testing/selftests/mm/rmap.c | 45 ++++++++++++++++++++++++++++++-
> 1 file changed, 44 insertions(+), 1 deletion(-)
OK, somehow your changelog was pasted into the email Subject, so please
resend.
Please prefix the Subject: with something which tells readers what part
of the kernel is affected. eg,
:
: Subject: selfstests/mm/rmap: verify correct RMAP handling of COW pages after fork()
:
Then enter the details in the changelog body, eg:
:
: Before a write, parent and child share the same PFN. After a write, the
: child’s PFN differs. Check this to confirm proper COW duplication.
:
prev parent reply other threads:[~2025-10-14 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 19:49 Itamar-Dalal
2025-10-14 21:29 ` Andrew Morton [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=20251014142957.4253f2fc62e9e49bfc4433ab@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=dalalitamar@gmail.com \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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