From: Andrew Morton <akpm@linux-foundation.org>
To: Dev Jain <dev.jain@arm.com>
Cc: shuah@kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Anshuman.Khandual@arm.com
Subject: Re: [PATCH] selftests/mm: Confirm VA exhaustion without reliance on correctness of mmap()
Date: Thu, 21 Mar 2024 14:51:46 -0700 [thread overview]
Message-ID: <20240321145146.a3ce8a1e247371e33a437978@linux-foundation.org> (raw)
In-Reply-To: <20240321103522.516097-1-dev.jain@arm.com>
On Thu, 21 Mar 2024 16:05:22 +0530 Dev Jain <dev.jain@arm.com> wrote:
> Currently, VA exhaustion is being checked by passing a hint to mmap() and
> expecting it to fail. This patch makes a stricter test by successful write()
> calls from /proc/self/maps to a dump file, confirming that a free chunk is
> indeed not available.
What's wrong with the current approach?
next prev parent reply other threads:[~2024-03-21 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 10:35 [PATCH] selftests/mm: Confirm VA exhaustion without reliance on correctness of mmap() Dev Jain
2024-03-21 21:51 ` Andrew Morton [this message]
2024-03-22 5:12 ` Dev Jain
2024-03-22 19:19 ` Andrew Morton
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=20240321145146.a3ce8a1e247371e33a437978@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Anshuman.Khandual@arm.com \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox