Bug 77712

Current MetaAllocator concept, always coalesces adjacent free spaces, doesn't meet memory management of Linux kernel. In a certain case Linux kernel doesn't regard contiguous virtual memory areas as one but two. Let's assume that mmap is called by MetaAllocator three times like below. 1. 8KB allocated from 0x41000000 to 0x41002000 by the 1st mmap call 2. 8KB allocated from 0x41004000 to 0x41006000 by the 2nd mmap call 3. 8KB allocated from 0x41002000 to 0x41004000 by the 3rd mmap call These virtual memory areas(VMAs) above are contiguous from 0x41000000 to 0x41006000, but the kernel merges only the third allocated 8KB with the first allocated 8KB although the second one is adjacent to the third. Because newly allocated VMA can be coalesced with the previously allocated and it's not allowed between previously allocated VMAs which internally have different information about annoymous pages. But current MetaAllocator is not considered on this kernel operation, thereby it just coalesces adjacent spaces when those are freed. This different mergence operation between MetaAllocator and Linux kernel finally causes the problem during cache flush. MetaAllocator hands over coalesced free space that the kernel regards it just as parts of two separated VMAs. The free space, coalesced by MetaAllocator, will be filled with JIT and cache flush will be run before the execution. At that time the flush range of the coalesced space is not guaranteed by kernel. It means inconsistency of data and instruction cache, and nobody knows what happens when this JIT code runs. The bottom line is that routines, handling this kernel operation, is necessary in MetaAllocator.