linux-kernel - Re: [PATCH v2] mlock.2: mlock2.2: Add entry to for new mlock2 syscall

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Sep 2015 11:31:49 +0200
From:	Vlastimil Babka <vbabka@...e.cz>
To:	Eric B Munson <emunson@...mai.com>, mtk.manpages@...il.com
Cc:	Michal Hocko <mhocko@...e.cz>, Jonathan Corbet <corbet@....net>,
	linux-man@...r.kernel.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] mlock.2: mlock2.2: Add entry to for new mlock2 syscall

On 08/31/2015 04:20 PM, Eric B Munson wrote:
> Update the mlock.2 man page with information on mlock2() and the new
> mlockall() flag MCL_ONFAULT.
> 
> Signed-off-by: Eric B Munson <emunson@...mai.com>
> Acked-by: Michal Hocko <mhocko@...e.com>

Looks like I acked v1 too late and not v2, so:

Acked-by: Vlastimil Babka <vbabka@...e.cz>

However, looks like it won't be in Linux 4.3 so that part is outdated.
Also, what about glibc wrapper for mlock2()? Does it have to come before or
after the manpage and who gets it in?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/