From: Mike Rapoport > Sent: 03 December 2020 06:58 > > On Wed, Dec 02, 2020 at 08:49:06PM +0200, Topi Miettinen wrote: > > On 1.12.2020 23.45, Topi Miettinen wrote: > > > Memory mappings inside kernel allocated with vmalloc() are in > > > predictable order and packed tightly toward the low addresses. With > > > new kernel boot parameter 'randomize_vmalloc=1', the entire area is > > > used randomly to make the allocations less predictable and harder to > > > guess for attackers. Isn't that going to horribly fragment the available address space and make even moderate sized allocation requests fail (or sleep). I'm not even sure that you need to use 'best fit' rather than 'first fit'. 'best fit' is certainly a lot better for a simple linked list user space malloc. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
