This issue can be fixed by this commit upstream:
commit 6c4bf3a75f4ba17503bc2d8ba91a7514fdae995e
Author: Avinesh Kumar <email address hidden>
Date: Wed Jan 24 14:26:02 2024 +0100
mmap04.c: Avoid vma merging
We hit a scenario where new mapping was merged with existing mapping of
same permission and the return address from the mmap was hidden in the
merged mapping in /proc/self/maps, causing the test to fail.
To avoid this, we first create a 2-page mapping with the different
permissions, and then remap the 2nd page with the perms being tested.
Link: https://<email address hidden>/
Reported-by: Martin Doucha <email address hidden>
Reviewed-by: Martin Doucha <email address hidden>
Reviewed-by: Petr Vorel <email address hidden>
Signed-off-by: Avinesh Kumar <email address hidden>
This issue can be fixed by this commit upstream: 503bc2d8ba91a75 14fdae995e
commit 6c4bf3a75f4ba17
Author: Avinesh Kumar <email address hidden>
Date: Wed Jan 24 14:26:02 2024 +0100
mmap04.c: Avoid vma merging
We hit a scenario where new mapping was merged with existing mapping of
same permission and the return address from the mmap was hidden in the
merged mapping in /proc/self/maps, causing the test to fail.
To avoid this, we first create a 2-page mapping with the different
permissions, and then remap the 2nd page with the perms being tested.
Link: https://<email address hidden>/
Reported-by: Martin Doucha <email address hidden>
Reviewed-by: Martin Doucha <email address hidden>
Reviewed-by: Petr Vorel <email address hidden>
Signed-off-by: Avinesh Kumar <email address hidden>