man2/syscalls.2: Add prlimit64.
PATCH 1/1 man2/syscalls.2: Add prlimit64.
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.
man2/syscalls.2 +1 -0
@@ -406,6 +406,7 @@ renamed "pread64" in 2.6 T} \fBpreadv\fP(2) 2.6.30 \fBprlimit\fP(2) 2.6.36 +\fBprlimit64\fP(2) 2.6.36 \fBprocess_vm_readv\fP(2) 3.2 \fBprocess_vm_writev\fP(2) 3.2 \fBpselect6\fP(2) 2.6.16
---
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 12 lines · Carlos O'Donell
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).
Quoted 4 lines
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 :-).
Cheers,
Michael
Signature · 7 lines
Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 13 lines · Michael Kerrisk (man-pages)
Quoted 12 lines · Carlos O'Donell
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).
Quoted 7 lines
Quoted 4 lines
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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html