From: Dev Jain <dev.jain@arm.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Shuah Khan" <shuah@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"David Hildenbrand" <david@redhat.com>,
"Ryan Roberts" <ryan.roberts@arm.com>
Cc: linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] selftests/mm: virtual_address_range: mmap() without PROT_WRITE
Date: Fri, 10 Jan 2025 21:17:01 +0530 [thread overview]
Message-ID: <9ed49333-b5fc-40c9-a8e4-fb3fc4af9089@arm.com> (raw)
In-Reply-To: <20250110-virtual_address_range-tests-v2-1-262a2bf3c3d0@linutronix.de>
On 10/01/25 6:35 pm, Thomas Weißschuh wrote:
> When mapping a larger chunk than physical memory is available with
> PROT_WRITE and overcommit is disabled, the mapping will fail.
> This will prevent the test from running on systems with less then ~1GiB
> of memory and triggering an inscrutinable test failure.
> As the mappings are never written to anyways, the flag can be removed.
>
> Fixes: 010409649885 ("selftests/mm: confirm VA exhaustion without reliance on correctness of mmap()")
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Thanks! FWIW:
Acked-by: Dev Jain <dev.jain@arm.com>
next prev parent reply other threads:[~2025-01-10 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 13:05 [PATCH v2 0/3] selftests/mm: virtual_address_range: Reduce memory usage and avoid VVAR access Thomas Weißschuh
2025-01-10 13:05 ` [PATCH v2 1/3] selftests/mm: virtual_address_range: mmap() without PROT_WRITE Thomas Weißschuh
2025-01-10 15:28 ` David Hildenbrand
2025-01-10 15:47 ` Dev Jain [this message]
2025-01-10 13:05 ` [PATCH v2 2/3] selftests/mm: virtual_address_range: Unmap chunks after validation Thomas Weißschuh
2025-01-10 15:37 ` David Hildenbrand
2025-01-10 13:05 ` [PATCH v2 3/3] selftests/mm: virtual_address_range: Avoid reading VVAR mappings Thomas Weißschuh
2025-01-10 15:41 ` David Hildenbrand
2025-01-13 9:09 ` Thomas Weißschuh
2025-01-13 9:30 ` David Hildenbrand
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=9ed49333-b5fc-40c9-a8e4-fb3fc4af9089@arm.com \
--to=dev.jain@arm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
/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