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
| ||
|
Date: Fri, 11 Sep 2015 17:16:05 +0200 From: Michal Hocko <mhocko@...nel.org> To: Eric B Munson <emunson@...mai.com> Cc: Vlastimil Babka <vbabka@...e.cz>, mtk.manpages@...il.com, 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 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 -- 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/
Powered by blists - more mailing lists