From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753109AbbIKPQL (ORCPT ); Fri, 11 Sep 2015 11:16:11 -0400 Received: from mail-wi0-f173.google.com ([209.85.212.173]:36936 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752846AbbIKPQI (ORCPT ); Fri, 11 Sep 2015 11:16:08 -0400 Date: Fri, 11 Sep 2015 17:16:05 +0200 From: Michal Hocko To: Eric B Munson Cc: Vlastimil Babka , mtk.manpages@gmail.com, Jonathan Corbet , linux-man@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] mlock.2: mlock2.2: Add entry to for new mlock2 syscall Message-ID: <20150911151605.GL3417@dhcp22.suse.cz> References: <1441030820-2960-1-git-send-email-emunson@akamai.com> <55F14E05.6020304@suse.cz> <20150911145712.GA3452@akamai.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150911145712.GA3452@akamai.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 11-09-15 10:57:12, Eric B Munson wrote: > On Thu, 10 Sep 2015, Vlastimil Babka wrote: [...] > > Also, what about glibc wrapper for mlock2()? Does it have to come before or > > after the manpage and who gets it in? > > V3 now has an updated version, hopefully mlock2 hits the 4.4 merge > window. > > I don't know about the glibc wrapper, are we expected to write one > ourselves? Will they even take it? They haven't been the most open > minded about taking wrappers for system calls that are unique to Linux > in the past. I do not think we really do care about the glibc wrapper. There are many syscalls which do not have it either (e.g. gettid). But I guess it would be worth noting this in the man page the same way as gettid does. -- Michal Hocko SUSE Labs