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, 24 Nov 2006 22:18:39 -0800 From: Michael Kerrisk <mtk-manpages@....net> To: lkml <linux-kernel@...r.kernel.org> Subject: man-pages-2.42 is released Gidday, I just released man-pages-2.41. This release is now available for download at: ftp://ftp.kernel.org/pub/linux/docs/manpages or mirrors: ftp://ftp.XX.kernel.org/pub/linux/docs/manpages and soon at: ftp://ftp.win.tue.nl/pub/linux-local/manpages Changes in this release that may be of interest to readers of this list include the following: Changes to individual pages --------------------------- brk.2 Evan Teran / mtk Add text describing behaviour of the Linux brk() system call and point out that the glibc brk() wrapper provides different behaviour. futex.2 mtk FUTEX_FD is scheduled for removal in June 2007. getaddrinfo.3 getnameinfo.3 Ulrich Drepper, with edits by mtk Add text describing Internationalized Domain Name extensions. ptrace.2 Chuck Ebbert Since Linux 2.6.18, the PID of the new process is also available for PTRACE_EVENT_VFORKDONE. core.5 mtk Linux 2.4.21 added core_pattern (which was already in 2.6). Noted a few more reasons why a core dump file might not be produced. Many things remain to be fixed -- help is appreciated. The list below notes outstanding FIXMEs from section 2 of the manual pages. Cheers, Michael ========== man2/epoll_wait.2 FIXME 2.6.19-rc5 has epoll_pwait(); this should be documented on this page. ========== man2/execve.2 FIXME add some statement about the effect on record locks (fcntl()). ========== man2/fcntl.2 FIXME According to POSIX.1-2001, O_SYNC should also be modifiable via fcntl(2), but currently Linux does not permit this See http://bugzilla.kernel.org/show_bug.cgi?id=5994 FIXME The statement that O_ASYNC can be used in open() does not match reality; setting O_ASYNC via open() does not seem to be effective. See http://bugzilla.kernel.org/show_bug.cgi?id=5993 FIXME Dec 04: some limited testing on alpha and ia64 seems to indicate that ANY negative PGID value will cause F_GETOWN to misinterpret the return as an error. Some other architectures seem to have the same range check as x86. Must document the reality on other architectures -- MTK ========== man2/futex.2 FIXME 2.6.18 adds (Ingo Molnar) priority inheritance support: FUTEX_LOCK_PI, FUTEX_UNLOCK_PI, and FUTEX_TRYLOCK_PI. These need to be documented in the manual page. Probably there is sufficient material in the kernel source file Documentation/pi-futex.txt. ========== man2/get_mempolicy.2 FIXME writeme -- no errors are listed on this page ========== man2/madvise.2 FIXME 2.6.16 added MADV_REMOVE, MADV_DONTFORK, and MADV_DOFORK. These need to be documented. MADV_DONTFORK /* don't inherit across fork */ MADV_DOFORK /* do inherit across fork */ A discussion of MADV_DONTFORK and MADV_DOFORK can be found at http://lwn.net/Articles/171941/ ========== man2/mount.2 FIXME 2.6.15 added flags for "shared sub-tree" functionality: MS_UNBINDABLE, MS_PRIVATE, MS_SHARED, MS_SLAVE These need to be documented on this page. See Documentation/sharedsubtree.txt FIXME Say more about MS_MOVE FIXME Document MS_REC, available since 2.4.11. This flag has meaning in conjunction with MS_BIND and also with the shared sub-tree flags. FIXME Can MNT_FORCE result in data loss? According to the Solaris manual page it can cause data loss on Solaris. If the same holds on Linux, then this should be documented. ========== man2/mprotect.2 FIXME Document MAP_GROWSUP and MAP_GROWSDOWN ========== man2/open.2 FIXME? The O_NOATIME flag also affects the treatment of st_atime by mmap() and readdir(2), MTK, Dec 04. FIXME Check bugzilla report on open(O_ASYNC) See http://bugzilla.kernel.org/show_bug.cgi?id=5993 ========== man2/path_resolution.2 FIXME say something about filesystem mounted read-only ? FIXME say something about immutable files FIXME say something about ACLs ========== man2/quotactl.2 FIXME There is much that is missing and/or out of date in this page. As things stand the page more or less documents Linux 2.2 reality: Linux 2.2 has: Q_GETQUOTA Q_GETSTATS Q_QUOTAOFF Q_QUOTAON Q_RSQUASH (not currently documented) Q_SETQLIM Q_SETQUOTA Q_SETUSE Q_SYNC Linux 2.4 has: Q_COMP_QUOTAOFF Q_COMP_QUOTAON Q_COMP_SYNC Q_GETFMT Q_GETINFO Q_GETQUOTA Q_QUOTAOFF Q_QUOTAON Q_SETINFO Q_SETQUOTA Q_SYNC Q_V1_GETQUOTA Q_V1_GETSTATS Q_V1_RSQUASH Q_V1_SETQLIM Q_V1_SETQUOTA Q_V1_SETUSE Q_V2_GETINFO Q_V2_GETQUOTA Q_V2_SETFLAGS Q_V2_SETGRACE Q_V2_SETINFO Q_V2_SETQUOTA Q_V2_SETUSE Q_XGETQSTAT Q_XGETQUOTA Q_XQUOTAOFF Q_XQUOTAON Q_XQUOTARM Q_XSETQLIM Linux 2.6.16 has: Q_GETFMT Q_GETINFO Q_GETQUOTA Q_QUOTAOFF Q_QUOTAON Q_SETINFO Q_SETQUOTA Q_SYNC Q_XGETQSTAT Q_XGETQUOTA Q_XQUOTAOFF Q_XQUOTAON Q_XQUOTARM Q_XQUOTASYNC Q_XSETQLIM ========== man2/select.2 FIXME select() (and pselect()?) also modify the timeout on an EINTR error return; POSIX.1-2001 doesn't permit this. ========== man2/send.2 FIXME? document MSG_PROXY (which went away in 2.3.15) ========== man2/set_mempolicy.2 FIXME writeme -- no errors are listed on this page ========== man2/shmop.2 FIXME What does "failing attach at brk" mean? (Is this phrase just junk?) FIXME A good explanation of the rationale for the existence of SHMLBA would be useful here FIXME That last sentence isn't true for all Linux architectures (i.e., SHMLBA != PAGE_SIZE for some architectures) -- MTK, Nov 04 -- Michael Kerrisk maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 Want to help with man page maintenance? Grab the latest tarball at http://www.kernel.org/pub/linux/docs/manpages/ read the HOWTOHELP file and grep the source files for 'FIXME'. - 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