Thread (21 messages) 21 messages, 4 authors, 2017-11-14

Re: linux-next: Tree for Nov 7

flat view

From: Michal Hocko <mhocko@kernel.org>
Date: 2017-11-13 15:49:45
Also in: linux-arm-kernel, linux-mips, linux-next, linux-sh, lkml, sparclinux

On Mon 13-11-17 16:16:41, Michal Hocko wrote:
On Mon 13-11-17 13:00:57, Michal Hocko wrote:
[...]
quoted
Yes, I have mentioned that in the previous email but the amount of code
would be even larger. Basically every arch which reimplements
arch_get_unmapped_area would have to special case new MAP_FIXED flag to
do vma lookup.
It turned out that this might be much more easier than I thought after
all. It seems we can really handle that in the common code. This would
mean that we are exposing a new functionality to the userspace though.
Myabe this would be useful on its own though. Just a quick draft (not
even compile tested) whether this makes sense in general. I would be
worried about unexpected behavior when somebody set other bit without a
good reason and we might fail with ENOMEM for such a call now.
Hmm, the bigger problem would be the backward compatibility actually. We
would get silent corruptions which is exactly what the flag is trying
fix. mmap flags handling really sucks. So I guess we would have to make
the flag internal only :/

-- 
Michal Hocko
SUSE Labs
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help