On 06/17/2014 02:18 PM, Michael Kerrisk (man-pages) wrote: > On 06/17/2014 04:41 PM, Carlos O'Donell wrote: >> While trying to reconcile the new features in glibc with the >> documented entries in the linux kernel man pages I noticed that >> glibc exports prlimit64 for use by 32-bit applications (as does >> the linux kernel), but that prlimit64 was not defined in the >> syscalls list or in the prlimit-related page. >> >> This is not the complete fix for this, but I don't have the time >> to explain why and when prlimit64 should be used (or how it should >> be used safely). Therefore I'm just patching the syscalls.2 list >> to show that prlimit64 exists and was added in 2.6.36 (verified >> with git by checking out the tags before and after). >> >> Unless you've purposely excluded prlimit64 to avoid telling users >> about it because it's complicated, please apply. >> >> Patch against master. > > Thanks, Carlos. Applied. When you one day explain it, probably > I will also get a bit of an educations :-). It's the `struct rlimit64`-equivalent syscall for the kernel. Given that prlimit and prlimit64 were added at the same time glibc's prlimit function always calls prlimit64 and converts where possible the struct rlimit64 to a struct rlimit handling overflows and nasty error cases. So prlimit is not a wrapper, but prlimit64 *is* just a syscall wrapper. Thus the complexity and probably verbose notes we'll need to add for direct usage of prlimit64. Cheers, Carlos. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
