diff options
| author | Michal Hocko <mhocko@suse.cz> | 2015-06-25 01:57:50 +0200 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2015-06-25 02:49:44 +0200 |
| commit | 9b012a29a300ea780d919205906d00d15cc6286e (patch) | |
| tree | bfeef7ea3414bab1035fb8bbfd08c3d7b368139d /arch | |
| parent | mm: nommu: refactor debug and warning prints (diff) | |
| download | linux-9b012a29a300ea780d919205906d00d15cc6286e.tar.xz linux-9b012a29a300ea780d919205906d00d15cc6286e.zip | |
Documentation/vm/unevictable-lru.txt: clarify MAP_LOCKED behavior
There is a very subtle difference between mmap()+mlock() vs
mmap(MAP_LOCKED) semantic. The former one fails if the population of the
area fails while the later one doesn't. This basically means that
mmap(MAPLOCKED) areas might see major fault after mmap syscall returns
which is not the case for mlock. mmap man page has already been altered
but Documentation/vm/unevictable-lru.txt deserves a clarification as well.
Signed-off-by: Michal Hocko <mhocko@suse.cz>
Reported-by: David Rientjes <rientjes@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions