tools/testing: expand mremap testing
Status from this message: [merged mm-stable] tools-testing-selftests-explicitly-test-split-multi-vma-mremap-move.patch removed from -mm tree
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 All 3 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | tools/testing/selftests: add mremap() shrink test for multiple VMAstools/ | +82 | 0 replies | Applied |
| 2/3 | tools/testing/selftests: test MREMAP_DONTUNMAP on multiple VMA movetools/ | +19 | 0 replies | Applied |
| 3/3 | tools/testing/selftests: explicitly test split multi VMA mremap movetools/ | +126 | 0 replies | Applied |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] tools/testing: expand mremap testing
Expand our mremap() testing to further assert that behaviour is as expected.
There is a poorly documented mremap() feature whereby it is possible to mremap() multiple VMAs (even with gaps) when shrinking, as long as the resultant shrunk range spans only a single VMA.
So we start by asserting this behaviour functions correctly both with an in-place shrink and a shrink/move.
Next, we further test the newly introduced ability to mremap() multiple VMAs when performing a MAP_FIXED move (that is without the size being changed), firstly by asserting that MREMAP_DONTUNMAP has no bearing on this behaviour.
Finally, we explicitly test that such moves, when splitting source VMAs, function correctly.
Lorenzo Stoakes (3):
tools/testing/selftests: add mremap() shrink test for multiple VMAs tools/testing/selftests: test MREMAP_DONTUNMAP on multiple VMA move tools/testing/selftests: explicitly test split multi VMA mremap move
tools/testing/selftests/mm/mremap_test.c | 235 ++++++++++++++++++++++- 1 file changed, 225 insertions(+), 10 deletions(-)
--
2.50.1