On Fri, Jul 11, 2025 at 09:17:27AM +0100, Mark Brown wrote:
On Mon, Jul 07, 2025 at 06:27:52AM +0100, Lorenzo Stoakes wrote:
Historically we've made it a uAPI requirement that mremap() may only operate on a single VMA at a time.
For instances where VMAs need to be resized, this makes sense, as it becomes very difficult to determine what a user actually wants should they indicate a desire to expand or shrink the size of multiple VMAs (truncate? Adjust sizes individually? Some other strategy?).
I'm seeing failures in the mremap_dontunmap test in -next on Rasperry Pi 4 which bisect down to this patch. The test logging isn't super helpful here sadly:
Same thing on Orion O6 (a more modern ARM v9 system with more RAM than my Pi):
https://lava.sirena.org.uk/scheduler/job/1556807
and Avenger 96 (which is 32 bit arm):