Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965170AbbEMOiZ (ORCPT ); Wed, 13 May 2015 10:38:25 -0400 Received: from cantor2.suse.de ([195.135.220.15]:56432 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964786AbbEMOiW (ORCPT ); Wed, 13 May 2015 10:38:22 -0400 From: Michal Hocko To: Michael Kerrisk Cc: Andrew Morton , Linus Torvalds , David Rientjes , LKML , Linux API , Subject: [PATCH 0/2] man-pages: clarify MAP_LOCKED semantic Date: Wed, 13 May 2015 16:38:10 +0200 Message-Id: <1431527892-2996-1-git-send-email-miso@dhcp22.suse.cz> X-Mailer: git-send-email 2.1.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 708 Lines: 14 Hi, during the previous discussion http://marc.info/?l=linux-mm&m=143022313618001&w=2 it was made clear that making mmap(MAP_LOCKED) semantic really have mlock() semantic is too dangerous. Even though we can try to reduce the failure space the mmap man page should make it really clear about the subtle distinctions between the two. This is what that first patch does. The second patch is a small clarification for MAP_POPULATE based on David Rientjes feedback. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/