Re: [BUG] get_unmapped_area() change -> non booting machine

[Jamie Lokier]

Linus Torvalds wrote:
> One option is to mark the brk() VMA's as being grow-up (which they are), 
> and make get_unmapped_area() realize that it should avoid trying to 
> allocate just above grow-up segments or just below grow-down segments. 
> That's still something of a special case, but at least it's not "magic" 
> any more, now it's more of a "makes sense".

That reminds me.  What happens when grow-down stack VMAs finally bump
into another VMA.  Is there an unmapped guard page retained to segfault
the program, or does the program silently start overwriting the VMA it
bumped into?

-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/