diff options
| author | Dev Jain <[email protected]> | 2024-03-21 16:05:22 +0530 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2024-04-25 20:56:01 -0700 |
| commit | 0104096498858346e3ac0668add1bf682461d4aa (patch) | |
| tree | 89772645074aac8661d6d5bac0a37e10eb2fcbdb /tools/perf/scripts/python/bin | |
| parent | 42a346b41c5b17d2fd609279e0dd0a4257d8fba0 (diff) | |
selftests/mm: confirm VA exhaustion without reliance on correctness of mmap()
Currently, VA exhaustion is being checked by passing a hint to mmap() and
expecting it to fail.
While populating the lower VA space, mmap() fails because we have
exhausted the space.
Then, in validate_lower_address_hint(), because mmap() fails, we
confirm that we have indeed exhausted the space. There is a circular
logic involved here.
Assume that there is a bug in mmap(), also assume that it exists
independent of whether you pass a hint address or not; that for some
reason it is not able to find a 1GB chunk. My idea is to assert the
exhaustion against some other method.
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.
[[email protected]: replace SZ_1GB with MAP_CHUNK_SIZE, tidy-up]
Link: https://lkml.kernel.org/r/[email protected]
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Dev Jain <[email protected]>
Cc: Anshuman Khandual <[email protected]>
Cc: Shuah Khan <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions