# Re: \[PATCH 1/2\] mmap.2: clarify MAP\_LOCKED semantic - From: Peter Zijlstra \ - Date: 2016-05-11 11:18:12 - List: linux-api - Page: https://ratatoskr.run/linux-api/2016/05/4749985 - Thread: https://ratatoskr.run/linux-api/2015/05/4492693/t.md ```text On 05/11/2016 01:07 PM, Peter Zijlstra wrote: > On 05/13/2015 04:38 PM, Michal Hocko wrote: >> >> This patch makes the semantic of MAP_LOCKED explicit and suggest using >> mmap + mlock as the only way to guarantee no later major page faults. >> > > URGH, this really blows chunks. It basically means MAP_LOCKED is pointless cruft and we might as well remove it. > > Why not fix it proper? OK; after having been pointed at this discussion, it seems I reacted rather too hasty in that I didn't read all the previous threads. From that it appears fixing this proper is indeed rather hard, and we should indeed consider MAP_LOCKED broken. At which point I would've worded the manpage update stronger, but alas. Sorry for the noise. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org ```