linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <shuah@kernel.org>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>,
	Jann Horn <jannh@google.com>
Subject: Re: [PATCH] selftests/mm: add fork CoW guard page test
Date: Thu, 5 Dec 2024 14:19:41 -0500	[thread overview]
Message-ID: <qbzzv3lz62it6gitcttsxe2f2i7uq56pz6sfcbjtopatryeukn@hfy3d3l2uvoy> (raw)
In-Reply-To: <20241205190748.115656-1-lorenzo.stoakes@oracle.com>

* Lorenzo Stoakes <lorenzo.stoakes@oracle.com> [241205 14:07]:
> When we fork anonymous pages, apply a guard page then remove it, the
> previous CoW mapping is cleared.
> 
> This might not be obvious to an outside observer without taking some time
> to think about how the overall process functions, so document that this is
> the case through a test, which also usefully asserts that the behaviour is
> as we expect.
> 
> This is grouped with other, more important, fork tests that ensure that
> guard pages are correctly propagated on fork.
> 
> Fix a typo in a nearby comment at the same time.
> 
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>

Nice to see some more testing going in.

Reviewed-by: Liam R. Howlett <Liam.Howlett@Oracle.com>

> ---
>  tools/testing/selftests/mm/guard-pages.c | 73 +++++++++++++++++++++++-
>  1 file changed, 72 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/mm/guard-pages.c b/tools/testing/selftests/mm/guard-pages.c
> index 7cdf815d0d63..d8f8dee9ebbd 100644
> --- a/tools/testing/selftests/mm/guard-pages.c
> +++ b/tools/testing/selftests/mm/guard-pages.c
> @@ -990,7 +990,7 @@ TEST_F(guard_pages, fork)
>  		   MAP_ANON | MAP_PRIVATE, -1, 0);
>  	ASSERT_NE(ptr, MAP_FAILED);
> 
> -	/* Establish guard apges in the first 5 pages. */
> +	/* Establish guard pages in the first 5 pages. */
>  	ASSERT_EQ(madvise(ptr, 5 * page_size, MADV_GUARD_INSTALL), 0);
> 
>  	pid = fork();
> @@ -1029,6 +1029,77 @@ TEST_F(guard_pages, fork)
>  	ASSERT_EQ(munmap(ptr, 10 * page_size), 0);
>  }
> 
> +/*
> + * Assert expected behaviour after we fork populated ranges of anonymous memory
> + * and then guard and unguard the range.
> + */
> +TEST_F(guard_pages, fork_cow)
> +{
> +	const unsigned long page_size = self->page_size;
> +	char *ptr;
> +	pid_t pid;
> +	int i;
> +
> +	/* Map 10 pages. */
> +	ptr = mmap(NULL, 10 * page_size, PROT_READ | PROT_WRITE,
> +		   MAP_ANON | MAP_PRIVATE, -1, 0);
> +	ASSERT_NE(ptr, MAP_FAILED);
> +
> +	/* Populate range. */
> +	for (i = 0; i < 10 * page_size; i++) {
> +		char chr = 'a' + (i % 26);
> +
> +		ptr[i] = chr;
> +	}
> +
> +	pid = fork();
> +	ASSERT_NE(pid, -1);
> +	if (!pid) {
> +		/* This is the child process now. */
> +
> +		/* Ensure the range is as expected. */
> +		for (i = 0; i < 10 * page_size; i++) {
> +			char expected = 'a' + (i % 26);
> +			char actual = ptr[i];
> +
> +			ASSERT_EQ(actual, expected);
> +		}
> +
> +		/* Establish guard pages across the whole range. */
> +		ASSERT_EQ(madvise(ptr, 10 * page_size, MADV_GUARD_INSTALL), 0);
> +		/* Remove it. */
> +		ASSERT_EQ(madvise(ptr, 10 * page_size, MADV_GUARD_REMOVE), 0);
> +
> +		/*
> +		 * By removing the guard pages, the page tables will be
> +		 * cleared. Assert that we are looking at the zero page now.
> +		 */
> +		for (i = 0; i < 10 * page_size; i++) {
> +			char actual = ptr[i];
> +
> +			ASSERT_EQ(actual, '\0');
> +		}
> +
> +		exit(0);
> +	}
> +
> +	/* Parent process. */
> +
> +	/* Parent simply waits on child. */
> +	waitpid(pid, NULL, 0);
> +
> +	/* Ensure the range is unchanged in parent anon range. */
> +	for (i = 0; i < 10 * page_size; i++) {
> +		char expected = 'a' + (i % 26);
> +		char actual = ptr[i];
> +
> +		ASSERT_EQ(actual, expected);
> +	}
> +
> +	/* Cleanup. */
> +	ASSERT_EQ(munmap(ptr, 10 * page_size), 0);
> +}
> +
>  /*
>   * Assert that forking a process with VMAs that do have VM_WIPEONFORK set
>   * behave as expected.
> --
> 2.47.1


      reply	other threads:[~2024-12-05 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 19:07 Lorenzo Stoakes
2024-12-05 19:19 ` Liam R. Howlett [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=qbzzv3lz62it6gitcttsxe2f2i7uq56pz6sfcbjtopatryeukn@hfy3d3l2uvoy \
    --to=liam.howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --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=shuah@kernel.org \
    --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