Various pages
Alain Portal
- Formating fixes.
+ Formatting fixes.
mlock.2
mprotect.2
strerror.3
mtk, after a note from Daniele Giacomini
- Modify SYNOPSIS to show protoypes of both versions of strerror_r(),
+ Modify SYNOPSIS to show prototypes of both versions of strerror_r(),
and make other small clarifications of the description regarding
the two versions.
proc.5
mtk
- The vaious CPU time fields in /proc/stat and /proc/PID/stat
+ The various CPU time fields in /proc/stat and /proc/PID/stat
return time in clock ticks (USER_HZ, cputime_to_clock_t(),
sysconf(_SC_CLK_TCK)).
Updated, clarified and expanded the description several
Michael Kerrisk
Global fix: s/(3)/(2)/ in section number xrefs for timer_*() API
The POSIX timers API is implemented (mostly) within the kernel,
- so thse interfaces are system calls. Although there are as yet
+ so these interfaces are system calls. Although there are as yet
no man pages, when they are added they should be in Section 2,
not 3. Therefore fix those pages that currently refer to these
interfaces as being in Section 3.
Major updates
Update the page to consolidate information from the
outdated man-pages quotactl.2 page and the quotactl.2
- page in the "quota-tools" pachage. The page in "quota-tools"
+ page in the "quota-tools" package. The page in "quota-tools"
has now been dropped by Jan Kara, so that there is just one
canonical quotactl.2 page (in pan-pages).
Michael Kerrisk
Change "should not overlap" to "must not overlap"
glibc 2.12 changed things so that applications that use memcpy() on
overlapping regions will encounter problems. (The standards have
- long said that the behavious is undefined if the memory areas
+ long said that the behaviors is undefined if the memory areas
overlap.)
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603144
Michael Kerrisk
BUGS: The O_SYNC and O_DSYNC flags are not modifiable using F_SETFL
Michael Kerrisk
- Add susbsections under BUGS
+ Add subsections under BUGS
There's several bugs listed. It's helpful to mark
them separately.
Michael Kerrisk
project generally focuses on only Linux kernel and
(g)libc interfaces, so this sync(8) page doesn't really
belong. Furthermore, coreutils has a sync(1) page which
- covers the same command. After dicussions on the
+ covers the same command. After discussions on the
coreutils list, I've decided to retire this page from
man-pages.
Michael Kerrisk
Add mention of seccomp(2) under PR_SET_SECCOMP
Michael Kerrisk
- Suggest /proc/PID/status "Seccomp" as alternative to PRCTL_GET_SECCOMP
+ Suggest /proc/PID/status "Seccomp" as alternative to PR_GET_SECCOMP
Michael Kerrisk
- SIGKILL can also occur PRCTL_GET_SECCOMP in SECCOMP_MODE_FILTER mode
+ SIGKILL can also occur PR_GET_SECCOMP in SECCOMP_MODE_FILTER mode
Kees Cook [Andy Lutomirski]
Document SECCOMP_MODE_FILTER vs EFAULT
This notes the distinction made between EINVAL and EFAULT when
Michael Kerrisk
Add F_OFD_SETLKW to list of restartable operations
+
+
+==================== Changes in man-pages-3.80 ====================
+
+Released: 2015-02-21, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Akihiro Motoki <amotoki@gmail.com>
+Andy Lutomirski <luto@amacapital.net>
+Bill McConnaughey <mcconnau@biochem.wustl.edu>
+Chris Mayo <aklhfex@gmail.com>
+Christophe Blaess <Christophe@blaess.fr>
+David Wilson <dw@botanicus.net>
+Denys Vlasenko <dvlasenk@redhat.com>
+Doug Goldstein <cardoe@gentoo.org>
+Eric Wong <normalperson@yhbt.net>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+J William Piggott <elseifthen@gmx.com>
+James Hunt <james.hunt@ubuntu.com>
+Jan Chaloupka <jchaloup@redhat.com>
+Jan Stancek <jstancek@redhat.com>
+Jeff Layton <jlayton@poochiereds.net>
+Jens Thoms Toerring <jt@toerring.de>
+Kevin Easton <kevin@guarana.org>
+Luke Faraone <lfaraone@debian.org>
+Mark Seaborn <mseaborn@chromium.org>
+Mathieu Malaterre <malat@debian.org>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Michal Hocko <mhocko@suse.cz>
+Minchan Kim <minchan@kernel.org>
+Patrick Horgan <phorgan1@gmail.com>
+Peng Haitao <penght@cn.fujitsu.com>
+Ralf Baechle <ralf@linux-mips.org>
+Rob Somers <uberkermit@gmail.com>
+Simon Paillard <spaillard@debian.org>
+Stephen Smalley <sds@tycho.nsa.gov>
+Tao Ma <tao.ma@oracle.com>
+Tobias Herzke <tobias.linuxpatches.2014@gi2.herzkes.de>
+Vince Weaver <vincent.weaver@maine.edu>
+Vlastimil Babka <vbabka@suse.cz>
+Zbigniew Brzeziński <zbigniew.brzezinski@student.put.poznan.pl>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+ioctl_fat.2
+ Heinrich Schuchardt [Michael Kerrisk]
+ New man page for the ioctl(2) FAT API
+ The ioctl(2) system call may be used to retrieve information about
+ the FAT file system and to set file attributes.
+
+madvise.2
+ Michael Kerrisk
+ Summary: this page has been significantly reorganised and rewritten
+ Michael Kerrisk
+ Recast discussion of 'advice' into two groups of values
+ madvise() is one of those system calls that has congealed over
+ time, as has the man page. It's helpful to split the discussion
+ of 'advice' into those flags into two groups:
+
+ * Those flags that are (1) widespread across implementations;
+ (2) have counterparts in posix_madvise(3); and (3) were present
+ in the initial Linux madvise implementation.
+ * The rest, which are values that (1) may not have counterparts
+ in other implementations; (2) have no counterparts in
+ posix_madvise(3); and (3) were added to Linux in more recent
+ times.
+ Michael Kerrisk
+ Explicitly list the five flags provided by posix_fadvise()
+ Over time, bit rot has afflicted this page. Since the original
+ text was written many new Linux-specific flags have been added.
+ So, now it's better to explicitly list the flags that
+ correspond to the POSIX analog of madvise().
+ Jan Chaloupka [Hugh Dickins, Michael Kerrisk]
+ Starting with Linux 3.5, more file systems support MADV_REMOVE
+ Michael Kerrisk
+ Split EINVAL error into separate cases
+ Michael Kerrisk
+ Explain MADV_REMOVE in terms of file hole punching
+ Michael Kerrisk
+ MADV_REMOVE can be applied only to shared writable mappings
+ Michael Kerrisk
+ MADV_REMOVE cannot be applied to locked or Huge TLB pages
+ Michael Kerrisk [Vlastimil Babka]
+ Clarify that MADV_DONTNEED has effect on pages only if it succeeds
+ Michael Kerrisk [Vlastimil Babka]
+ Clarifications for MADV_DONTNEED
+ Michael Kerrisk [Michal Hocko]
+ Improve MADV_DONTNEED description
+ Michael Kerrisk
+ MADV_DONTNEED cannot be applied to Huge TLB or locked pages
+ Michael Kerrisk [Vlastimil Babka]
+ Remove mention of "shared pages" as a cause of EINVAL for MADV_DONTNEED
+ Michael Kerrisk [Vlastimil Babka]
+ Note Huge TLB as a cause of EINVAL for MADV_DONTNEED
+ Michael Kerrisk [Minchan Kim]
+ Add mention of VM_PFNMAP in discussion of MADV_DONTNEED and MADV_REMOVE
+ Michael Kerrisk
+ Drop sentence saying that kernel may ignore 'advice'
+ The sentence creates misunderstandings, and does not really
+ add information.
+ Michael Kerrisk
+ Note that some Linux-specific 'advice' change memory-access semantics
+ Michael Kerrisk
+ NOTES: Remove crufty text about "command" versus "advice"
+ The point made in this fairly ancient text is more or less evident
+ from the DESCRIPTION, and it's not clear what "standard" is being
+ referred to.
+ Michael Kerrisk
+ Mention POSIX.1-2008 addition of POSIX_MADV_NOREUSE
+ Michael Kerrisk
+ Remove "POSIX.1b" from CONFORMING TO
+ Michael Kerrisk
+ Move mention of posix_fadvise() from CONFORMING TO to SEE ALSO
+ Michael Kerrisk
+ ERRORS: add EPERM error case for MADV_HWPOISON
+ Michael Kerrisk
+ Note that madvise() is nonstandard, but widespread
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+proc.5
+ Michael Kerrisk
+ (Briefly) document /proc/PID/attr/socketcreate
+ Michael Kerrisk
+ (Briefly) document /proc/PID/attr/keycreate
+ Michael Kerrisk [Stephen Smalley]
+ Document /proc/PID/attr/{current,exec,fscreate,prev}
+ Heavily based on Stephen Smalley's text in
+ https://lwn.net/Articles/28222/
+ From: Stephen Smalley <sds@epoch.ncsc.mil>
+ To: LKML and others
+ Subject: [RFC][PATCH] Process Attribute API for Security Modules
+ Date: 08 Apr 2003 16:17:52 -0400
+ Michael Kerrisk
+ Document /proc/sys/kernel/auto_msgmni
+
+socket.7
+ David Wilson [Michael Kerrisk]
+ Document SO_REUSEPORT socket option
+
+
+New and changed links
+---------------------
+
+get_thread_area.2
+ Andy Lutomirski
+ Make get_thread_area.2 a link to rewritten set_thread_area.2 page
+
+
+Changes to individual pages
+---------------------------
+
+time.1
+ Michael Kerrisk
+ Make option argument formatting consistent with other pages
+
+access.2
+ Denys Vlasenko
+ Explain how access() check treats capabilities
+ We have users who are terribly confused why their binaries
+ with CAP_DAC_OVERRIDE capability see EACCESS from access() calls,
+ but are able to read the file.
+
+ The reason is access() isn't the "can I read/write/execute this
+ file?" question, it is the "(assuming that I'm a setuid binary,)
+ can *the user who invoked me* read/write/execute this file?"
+ question.
+
+ That's why it uses real UIDs as documented, and why it ignores
+ capabilities when capability-endorsed binaries are run by non-root
+ (this patch adds this information).
+
+ To make users more likely to notice this less-known detail,
+ the patch expands the explanation with rationale for this logic
+ into a separate paragraph.
+
+arch_prctl.2
+set_thread_area.2
+get_thread_area.2
+ Andy Lutomirski
+ Improve TLS documentation
+ The documentation for set_thread_area was very vague. This
+ improves it, accounts for recent kernel changes, and merges
+ it with get_thread_area.2.
+
+ get_thread_area.2 now becomes a link.
+
+ While I'm at it, clarify the related arch_prctl.2 man page.
+
+cacheflush.2
+ Ralf Baechle
+ Update some portability details and bugs
+ Michael Kerrisk
+ Refer reader to BUGS in discussion of EINVAL error
+
+capget.2
+ Michael Kerrisk
+ Document V3 capabilities constants
+ Michael Kerrisk
+ Rewrite discussion of kernel versions that support file capabilities
+ File capabilities ceased to be optional in Linux 2.6.33.
+
+clone.2
+ Peng Haitao
+ Fix description of CLONE_PARENT_SETTID
+ CLONE_PARENT_SETTID only stores child thread ID in parent memory.
+
+clone.2
+execve.2
+ Kevin Easton
+ Document interaction of execve(2) with CLONE_FILES
+ This patch the fact that a successful execve(2) in a process that
+ is sharing a file descriptor table results in unsharing the table.
+
+ I discovered this through testing and verified it by source
+ inspection - there is a call to unshare_files() early in
+ do_execve_common().
+
+fcntl.2
+ Michael Kerrisk [Jeff Layton]
+ Clarify cases of conflict between traditional record and OFD locks
+ Verified by experiment on Linux 3.15 and 3.19rc4.
+
+fork.2
+ Michal Hocko
+ EAGAIN is not reported when task allocation fails
+ I am not sure why we have:
+
+ "EAGAIN fork() cannot allocate sufficient memory to copy
+ the parent's page tables and allocate a task structure
+ or the child."
+
+ The text seems to be there from the time when man-pages
+ were moved to git so there is no history for it.
+
+ And it doesn't reflect reality: the kernel reports both
+ dup_task_struct and dup_mm failures as ENOMEM to the
+ userspace. This seems to be the case from early 2.x times
+ so let's simply remove this part.
+ Heinrich Schuchardt
+ Child and parent run in separate memory spaces
+ fork.2 should clearly point out that child and parent
+ process run in separate memory spaces.
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+getpid.2
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+getxattr.2
+ Michael Kerrisk
+ Various rewordings plus one or two details clarified
+ Michael Kerrisk
+ Add pointer to example in listxattr(2)
+
+killpg.2
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+listxattr.2
+ Heinrich Schuchardt
+ Provide example program
+ Michael Kerrisk
+ Reword discussion of size==0 case
+ Michael Kerrisk
+ Add note on handling increases in sizes of keys or values
+ Michael Kerrisk
+ Remove mention of which filesystems implement ACLs
+ Such a list will only become outdated (as it already was).
+
+migrate_pages.2
+ Jan Stancek
+ Document EFAULT and EINVAL errors
+ I encountered these errors while writing testcase for migrate_pages
+ syscall for LTP (Linux test project).
+
+ I checked stable kernel tree 3.5 to see which paths return these.
+ Both can be returned from get_nodes(), which is called from:
+ SYSCALL_DEFINE4(migrate_pages, pid_t, pid, unsigned long, maxnode,
+ const unsigned long __user *, old_nodes,
+ const unsigned long __user *, new_nodes)
+
+ The testcase does following:
+ EFAULT
+ a) old_nodes/new_nodes is area mmaped with PROT_NONE
+ b) old_nodes/new_nodes is area not mmapped in process address
+ space, -1 or area that has been just munmmaped
+
+ EINVAL
+ a) maxnodes overflows kernel limit
+ b) new_nodes contain node, which has no memory or does not exist
+ or is not returned for get_mempolicy(MPOL_F_MEMS_ALLOWED).
+
+modify_ldt.2
+ Andy Lutomirski
+ Overhaul the documentation
+ This clarifies the behavior and documents all four functions.
+ Andy Lutomirski
+ Clarify the lm bit's behavior
+ The lm bit should never have existed in the first place. Sigh.
+
+mprotect.2
+ Mark Seaborn
+ Mention effect of READ_IMPLIES_EXEC personality flag
+ I puzzled over mprotect()'s effect on /proc/*/maps for a while
+ yesterday -- it was setting "x" without PROT_EXEC being specified.
+ Here is a patch to add some explanation.
+
+msgget.2
+ Michael Kerrisk
+ Add details of MSGMNI default value
+
+msgop.2
+ Michael Kerrisk
+ Clarify wording of MSGMAX and MSGMNB limits
+
+perf_event_open.2
+ Vince Weaver
+ Clarify PERF_EVENT_IOC_REFRESH behavior
+ Currently the PERF_EVENT_IOC_REFRESH ioctl, when applied to a group
+ leader, will refresh all children. Also if a refresh value of 0
+ is chosen then the refresh becomes infinite (never runs out).
+ Back in 2011 PAPI was relying on these behaviors but I was told
+ that both were unsupported and subject to being removed at any time.
+ (See https://lkml.org/lkml/2011/5/24/337 )
+ However the behavior has not been changed.
+
+ This patch updates the manpage to still list the behavior as
+ unsupported, but removes the inaccurate description of it
+ only being a problem with 2.6 kernels.
+
+prctl.2
+ Michael Kerrisk [Bill McConnaughey]
+ Mention file capabilities in discussion of PR_SET_DUMPABLE
+ Michael Kerrisk
+ Greatly expand discussion of "dumpable" flag
+ In particular, detail the interactions with
+ /proc/sys/fs/suid_dumpable.
+ Michael Kerrisk
+ Reorder paragraphs describing PR_SET_DUMPABLE
+ Michael Kerrisk
+ Mention SUID_DUMP_DISABLE and SUID_DUMP_USER under PR_SET_DUMPABLE
+ Michael Kerrisk
+ Executing a file with capabilities also resets the parent death signal
+
+ptrace.2
+ James Hunt
+ Explain behaviour should ptrace tracer call execve(2)
+ This behaviour was verified by reading the kernel source and
+ confirming the behaviour using a test program.
+ Denys Vlasenko
+ Add information on PTRACE_SEIZE versus PTRACE_ATTACH differences
+ Extend description of PTRACE_SEIZE with the short summary of its
+ differences from PTRACE_ATTACH.
+
+ The following paragraph:
+
+ PTRACE_EVENT_STOP
+ Stop induced by PTRACE_INTERRUPT command, or group-stop, or ini-
+ tial ptrace-stop when a new child is attached (only if attached
+ using PTRACE_SEIZE), or PTRACE_EVENT_STOP if PTRACE_SEIZE was used.
+
+ has an editing error (the part after last comma makes no sense).
+ Removing it.
+
+ Mention that legacy post-execve SIGTRAP is disabled by PTRACE_SEIZE.
+
+sched_setattr.2
+ Michael Kerrisk [Christophe Blaess]
+ SYNOPSIS: remove 'const' from 'attr' sched_getattr() argument
+
+semget.2
+ Michael Kerrisk
+ Note default value for SEMMNI and SEMMSL
+
+semop.2
+ Michael Kerrisk
+ Note defaults for SEMOPM and warn against increasing > 1000
+
+sendfile.2
+ Eric Wong
+ Caution against modifying sent pages
+
+setxattr.2
+ Michael Kerrisk
+ ERRORS: add ENOTSUP for invalid namespace prefix
+ Michael Kerrisk
+ Remove redundant text under ENOTSUP error
+ Michael Kerrisk
+ Note that zero-length attribute values are permitted
+ Michael Kerrisk
+ Rework text describing 'flags' argument
+
+stat.2
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+statfs.2
+ Michael Kerrisk [Jan Chaloupka]
+ Document the 'f_flags' field added in Linux 2.6.36
+ Michael Kerrisk
+ Clarify that 'statfs' structure has some padding bytes
+ The number of padding bytes has changed over tyme, as some
+ bytes are used, so describe this aspect of the structure
+ less explicitly.
+ Tao Ma
+ Add OCFS2_SUPER_MAGIC
+ Michael Kerrisk
+ Use __fsword_t in statfs structure definition
+ This more closely matches modern glibc reality.
+ Michael Kerrisk
+ Add a note on the __fsword_t type
+ Michael Kerrisk
+ Document 'f_spare' more vaguely
+
+wait.2
+ Michael Kerrisk
+ Note that waitpid() is a wrapper for wait4()
+ Michael Kerrisk
+ Note that wait() is a library function implemented via wait4()
+
+wait4.2
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+
+encrypt.3
+ Rob Somers
+ Improve code example
+ I (and some others) found that the original example code
+ did not seem to work as advertised. The new code (used by
+ permission of the original author, Jens Thoms Toerring)
+ was found on comp.os.linux.development.
+
+mktemp.3
+ Luke Faraone
+ DESCRIPTION reference to BUGS corrected
+ mktemp(3)'s DESCRIPTION referenced NOTES, but no such
+ section exists. Corrected to refer to BUGS.
+
+pthread_attr_setschedparam.3
+ Tobias Herzke
+ Describe EINVAL in ERRORS
+
+resolver.3
+host.conf.5
+ Simon Paillard
+ host.conf 'order' option deprecated, replaced by nsswitch.conf(5)
+ http://www.sourceware.org/bugzilla/show_bug.cgi?id=2389
+ http://repo.or.cz/w/glibc.git/commit/b9c65d0902e5890c4f025b574725154032f8120a
+
+ Reported at http://bugs.debian.org/270368,
+ http://bugs.debian.org/396633, and http://bugs.debian.org/344233.
+
+statvfs.3
+ Michael Kerrisk
+ Document missing 'f_flag' bit values
+ And reorganize information relating to which flags are in
+ POSIX.1.
+ Michael Kerrisk [Jan Chaloupka]
+ statvfs() now populates 'f_flag' from statfs()'s f_flag field
+ These changes came with glibc 2.13, and the kernel's addition of
+ a 'f_flags' field in Linux 2.6.36.
+
+syslog.3
+ Michael Kerrisk [Doug Goldstein]
+ Remove unneeded <stdarg.h>
+ vsyslog() does not need this.
+
+tzset.3
+ J William Piggott
+ Add offset format
+ tzset.3 does not illustrate the POSIX offset format.
+ Specifically, there is no indication in the manual
+ what the optional components of it are.
+
+random.4
+ Michael Kerrisk
+ Note maximum number of bytes returned by read(2) on /dev/random
+ Michael Kerrisk [Mathieu Malaterre]
+ Since Linux 3.16, reads from /dev/urandom return at most 32 MB
+ See https://bugs.debian.org/775328 and
+ https://bugzilla.kernel.org/show_bug.cgi?id=80981#c9
+
+core.5
+ Michael Kerrisk [Bill McConnaughey]
+ Executing a file that has capabilities also prevents core dumps
+ Michael Kerrisk
+ Document "%i" and "%I" core_pattern specifiers
+
+intro.5
+ Michael Kerrisk
+ Remove words "and protocols"
+ There are no protocol descriptions in Section 5. Protocols are
+ in Section 7.
+
+proc.5
+ Michael Kerrisk
+ Add reference to prctl(2) in discussion of /proc/sys/fs/suid_dumpable
+ And note that /proc/sys/fs/suid_dumpable defines the
+ value assigned to the process "dumpable" flag in certain
+ circumstances.
+ Michael Kerrisk
+ Note that CAP_SYS_ADMIN is required to list /proc/PID/map_files
+ This might however change in the future; see the Jan 2015 LKML thread:
+
+ Re: [RFC][PATCH v2] procfs: Always expose /proc/<pid>/map_files/
+ and make it readable
+
+resolv.conf.5
+ Michael Kerrisk
+ SEE ALSO: add nsswitch.conf(5)
+
+capabilities.7
+ Michael Kerrisk
+ Mention SECBIT_KEEP_CAPS as an alternative to prctl() PR_SET_KEEPCAPS
+ Chris Mayo
+ NOTES: add last kernel versions for obsolete options
+ The CONFIG_SECURITY_CAPABILITIES option was removed by
+ commit 5915eb53861c5776cfec33ca4fcc1fd20d66dd27
+
+ The CONFIG_SECURITY_FILE_CAPABILITIES option removed in
+ Linux 2.6.33 as already mentioned in DESCRIPTION.
+
+pthreads.7
+ Michael Kerrisk
+ SEE ALSO: add fork(2)
+
+unix.7
+ Jan Chaloupka
+ Mention SOCK_STREAM socket for ioctl_type of ioctl()
+ from https://bugzilla.redhat.com/show_bug.cgi?id=1110401.
+
+ unix.7 is not clear about socket type of ioctl_type argument of
+ ioctl() function. The description of SIOCINQ is applicable only
+ for SOCK_STREAM socket. For SOCK_DGRAM, udp(7) man page gives
+ correct description of SIOCINQ
+
+ldconfig.8
+ Michael Kerrisk
+ Place options in alphabetical order
+ Michael Kerrisk
+ Note glibc version number for '-l' option
+ Michael Kerrisk
+ Document -c/--format option
+ Michael Kerrisk
+ Add long form of some options
+ Michael Kerrisk [Patrick Horgan]
+ ld.so.conf uses only newlines as delimiters
+ mtk: confirmed by reading source of parse_conf() in
+ elf/ldconfig.c.
+ Michael Kerrisk
+ Document -V/--version option
+ Michael Kerrisk
+ Document -i/--ignore-aux-cache option
+
+ld.so.8
+ Michael Kerrisk
+ Relocate "Hardware capabilities" to be a subsection under notes
+ This is more consistent with standard man-pages headings
+ and layout.
+ Michael Kerrisk
+ (Briefly) document LD_TRACE_PRELINKING
+ Michael Kerrisk
+ Remove duplicate description of LD_BIND_NOT
+
+
+==================== Changes in man-pages-3.81 ====================
+
+Released: 2015-03-02, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Alexandre Oliva <aoliva@redhat.com>
+Carlos O'Donell <carlos@redhat.com>
+Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Peng Haitao <penght@cn.fujitsu.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+attributes.7
+ Alexandre Oliva, Michael Kerrisk [Carlos O'Donell]
+ New page describing POSIX safety concepts
+
+
+Global changes
+--------------
+
+Many pages
+ Peng Haitao, Michael Kerrisk
+ Reformat existing thread-safety information to use a
+ tabular format, rather than plain text.
+
+
+Changes to individual pages
+---------------------------
+
+mmap.2
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function mmap() and munmap() are thread safe.
+
+a64l.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+acos.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function acos(), acosf() and acosl() are thread safe.
+
+acosh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function acosh(), acoshf() and acoshl() are thread safe.
+
+addseverity.3
+ Ma Shimiao
+ ATTRIBUTES: Note function is thread-safe
+ The function addseverity() is thread safe.
+
+aio_cancel.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function aio_cancel() is thread safe.
+
+aio_fsync.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function aio_fsync() is thread safe.
+
+aio_read.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function aio_read() is thread safe.
+
+aio_suspend.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function aio_suspend() is thread safe.
+
+aio_write.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function aio_write() is thread safe.
+
+argz_add.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+
+asin.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function asin(), asinf() and asinl() are thread safe.
+
+assert.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+assert_perror.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+atan2.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function atan2(), atan2f() and atan2l() are thread safe.
+
+atanh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function atanh(), atanhf() and atanhl() are thread safe.
+
+backtrace.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+btowc.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function btowc() in glibc is thread safe.
+ Its marking matches glibc marking.
+
+cabs.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function cabs(), cabsf() and cabsl() are thread safe.
+
+cacos.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function cacos(), cacosf() and cacosl() are thread safe.
+
+cacosh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions cacosh(), cacoshf() and cacoshl() in glibc are
+ thread safe. Its markings match glibc markings.
+
+canonicalize_file_name.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The functions canonicalize_file_name() in glibc is thread safe.
+ Its marking matches glibc marking.
+
+carg.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function carg(), cargf() and cargl() are thread safe.
+
+casin.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions casin(), casinf() and casinl() are thread safe.
+ Their markings match glibc markings.
+
+casinh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions casinh(), casinhf() and casinhl() in glibc are
+ thread safe. Its markings match glibc markings.
+
+catan.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions catan(), catanf() and catanl() are thread safe.
+ Their markings match glibc markings.
+
+catanh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions catanh(), catanhf() and catanhl() in glibc are
+ thread safe. Its markings match glibc markings.
+
+catopen.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions catopen() and catclose() are thread safe.
+
+cfree.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function cfree() in glibc is thread safe.
+ Its marking matches glibc marking.
+
+clog10.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions clog10(), clog10f() and clog10l() in glibc are
+ thread safe. Its markings match glibc markings.
+
+clog.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function clog(), clogf() and clogl() are thread safe.
+
+closedir.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function closedir() in glibc is thread safe.
+ Its marking matches glibc marking.
+
+confstr.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function confstr() is thread safe.
+
+cosh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions cosh(), coshf() and coshl() in glibc are thread safe.
+ Its markings match glibc markings.
+
+cpow.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions cpow(), cpowf() and cpowl() in glibc are thread safe.
+ Its markings match glibc markings.
+
+crypt.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+ctermid.3
+ Ma Shimiao
+ Modify thread-safety information
+ According to the change of source code, ctermid's level has been
+ changed from MT-Unsafe to MT-Safe. After modifying, the marking
+ matches the glibc marking.
+
+drand48.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+drand48_r.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+ecvt.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be same as glibc manual.
+
+ecvt_r.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+encrypt.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+envz_add.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+exec.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions execl(), execlp(), execle(), execv(), execvp() and
+ execvpe() are thread safe.
+
+exit.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+exp10.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+
+exp2.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function exp2(), exp2f() and exp2l() are thread safe.
+
+exp.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function exp(), expf() and expl() are thread safe.
+
+fclose.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The function fclose() is thread safe.
+ Its marking matches glibc marking.
+
+fcloseall.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+fgetc.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+fgetwc.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+fgetws.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+fmod.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function fmod(), fmodf() and fmodl() are thread safe.
+
+fnmatch.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function fnmatch() is thread safe with exceptions.
+
+fopen.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+fopencookie.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+fread.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions fread() and fwrite() are thread safe.
+
+gamma.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are not thread-safe
+ The functions gamma(), gammaf() and gammal() are not thread safe.
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getcontext.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getcwd.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions getcwd(), getwd() and get_current_dir_name() are
+ thread safe.
+
+getdate.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getenv.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions getenv() and secure_getenv() are thread safe.
+
+getfsent.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are not thread-safe
+ The functions setfsent(), getfsent(), endfsent(), getfsspec()
+ and getfsfile() are not thread safe.
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getgrent.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getgrnam.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getgrouplist.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function getgrouplist() is thread safe with exceptions.
+
+getlogin.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getopt.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are not thread-safe
+ The functions getopt(), getopt_long() and getopt_long_only() are
+ not thread safe.
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getpass.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getpwent.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+getpwnam.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+gets.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+getw.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions getw() and putw() are thread safe.
+
+gnu_get_libc_version.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions gnu_get_libc_version() and gnu_get_libc_release()
+ are thread safe.
+
+hsearch.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+iconv.3
+ Peng Haitao
+ Modify thread-safety information
+
+inet.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread safe with exceptions
+ The functions inet_aton() and inet_addr() are thread safe with
+ exceptions.
+ The functions inet_network(), inet_ntoa(), inet_makeaddr(),
+ inet_lnaof() and inet_netof() are thread safe.
+ Modify thread-safety information
+ After researching and talking, we think inet_network() and
+ inet_ntoa() should be marked with locale.
+ After changing, the markings match glbc markings.
+
+inet_pton.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function inet_pton() is thread safe with exceptions.
+
+iswdigit.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswdigit() is thread safe with exceptions.
+
+iswgraph.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswgraph() is thread safe with exceptions.
+
+iswlower.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswlower() is thread safe with exceptions.
+
+iswprint.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswprint() is thread safe with exceptions.
+
+iswpunct.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswpunct() is thread safe with exceptions.
+
+iswspace.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswspace() is thread safe with exceptions.
+
+iswupper.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswupper() is thread safe with exceptions.
+
+iswxdigit.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function iswxdigit() is thread safe with exceptions.
+
+j0.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function j0(), j1f() jnl() and so on are thread safe.
+
+lio_listio.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+log10.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function log10(), log10f() and log10l() are thread safe.
+
+log2.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function log2(), log2f() and log2l() are thread safe.
+
+log.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function log(), logf() and logl() are thread safe.
+
+makecontext.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+makedev.3
+ Peng Haitao
+ ATTRIBUTES: Note macros that are thread-safe
+ The macros makedev(), major() and minor() are thread safe.
+
+malloc.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function malloc(), free(), calloc() and realloc() are
+ thread safe.
+
+mblen.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+mbstowcs.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+mbtowc.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is not thread-safe
+ The function mbtowc() is not thread safe.
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+mktemp.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function mktemp() is thread safe.
+
+mtrace.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are not thread-safe
+ The functions mtrace() and muntrace() are not thread safe.
+
+nan.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+nl_langinfo.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function nl_langinfo() is thread safe with exceptions.
+
+opendir.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+pow10.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function pow10(), pow10f() and pow10l() are thread safe.
+
+pow.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function pow(), powf() and powl() are thread safe.
+
+pthread_setcancelstate.3
+ Michael Kerrisk
+ Add async-signal-safety information
+
+ptsname.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+putenv.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-unsafe
+ The function putenv() is thread unsafe.
+
+puts.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions fputc(), fputs(), putc(), putchar() and puts() are
+ thread safe.
+
+putwchar.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+qecvt.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be same as glibc manual.
+
+rand.3
+ Peng Haitao
+ ATTRIBUTES: Note macros that are thread-safe
+ The functions rand(), rand_r() and srand() are thread safe.
+
+random_r.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+readdir.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be same as glibc manual.
+
+realpath.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+regex.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread safe with exceptions
+ The functions regcomp() and regexec() are thread safe with
+ exceptions.
+ The functions regerror() and regfree() are thread safe.
+
+remainder.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+scalb.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function scalb(), scalbf() and scalbl() are thread safe.
+
+setenv.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-unsafe
+ The function setenv() and unsetenv() are thread unsafe.
+
+siginterrupt.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+sigset.3
+ Peng Haitao
+ ATTRIBUTES: Note macros that are thread-safe
+ The functions sigset(), sighold(), sigrelse() and sigignore()
+ are thread safe.
+
+sinh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function sinh(), sinhf() and sinhl() are thread safe.
+
+sqrt.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function sqrt(), sqrtf() and sqrtl() are thread safe.
+
+stdarg.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+stdio_ext.3
+ Ma Shimiao
+ Modify thread-safety information
+ Change the thread safety information to be the same as glibc.
+
+strcasecmp.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread safe with exceptions
+ The functions strcasecmp() and strncasecmp() are thread safe
+ with exceptions.
+
+strerror.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+strfmon.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+strfry.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function strfry() is thread safe.
+
+strftime.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function strftime() is thread safe with exceptions.
+
+strptime.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function strptime() is thread safe with exceptions.
+
+strtok.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+strverscmp.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function strverscmp() is thread safe.
+
+strxfrm.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+syslog.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread safe with exceptions
+ The functions openlog() and closelog() are thread safe.
+ The functions syslog() and vsyslog() are thread safe with
+ exceptions.
+
+tempnam.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread-safe
+ The function tempnam() is thread safe.
+
+termios.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+ Ma Shimiao
+ Modify thread-safety information
+ As this is man page for Linux, we don't need thread safety
+ information for bsd
+
+tgamma.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions tgamma(), tgammaf() and tgammal() in glibc are
+ thread safe. Its markings match glibc markings.
+
+timegm.3
+ Peng Haitao
+ ATTRIBUTES: Note functions that are thread safe with exceptions
+ The functions timelocal() and timegm() are thread safe with
+ exceptions.
+
+tmpfile.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its markings match glibc markings.
+
+tmpnam.3
+ Peng Haitao
+ Modify thread-safety information
+ When the argument s is NULL, tmpnam() should be MT-Unsafe.
+
+toupper.3
+ Ma Shimiao
+ Modify thread-safety information
+ After researching and talking, we think toupper() and tolower()
+ should not be marked with locale.
+ After changing, the markings match glbc markings.
+
+tsearch.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The functions' markings match glibc markings.
+
+ttyname.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be same as glibc manual.
+
+tzset.3
+ Peng Haitao
+ ATTRIBUTES: Note function that is thread safe with exceptions
+ The function tzset() is thread safe with exceptions.
+
+wcsdup.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ Its marking matches glibc marking.
+
+wctomb.3
+ Ma Shimiao
+ Modify thread-safety information
+ As annotation in glibc manual is more detailed, change the
+ thread-safety information to be the same as glibc manual.
+
+y0.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The function y0(), y1f() ynl() and so on are thread safe.
+
+man-pages.7
+ Michael Kerrisk
+ Refer reader to attributes(7) for details of ATTRIBUTES section
+ Michael Kerrisk
+ SEE ALSO: add attributes(7)
+
+pthreads.7
+ Michael Kerrisk
+ SEE ALSO: add attributes(7)
+
+standards.7
+ Michael Kerrisk
+ SEE ALSO: add attributes(7)
+
+
+
+==================== Changes in man-pages-3.82 ====================
+
+Released: 2015-03-29, Paris
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Alban Crequy <alban.crequy@gmail.com>
+Andy Lutomirski <luto@amacapital.net>
+Bert Wesarg <bert.wesarg@googlemail.com>
+Bill Pemberton <wfp5p@worldbroken.com>
+Chris Delozier <c.s.delozier@gmail.com>
+David Madore <david.madore@ens.fr>
+Dmitry Deshevoy <mityada@gmail.com>
+Eric W. Biederman <ebiederm@xmission.com>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Jakub Wilk <jwilk@debian.org>
+Jann Horn <jann@thejh.net>
+Jason Vas Dias <jason.vas.dias@gmail.com>
+Josh Triplett <josh@joshtriplett.org>
+J William Piggott <elseifthen@gmx.com>
+Kees Cook <keescook@chromium.org>
+Konstantin Shemyak <konstantin@shemyak.com>
+Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
+Matt Turner <mattst88@gmail.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Michael Witten <mfwitten@gmail.com>
+Mikael Pettersson <mikpelinux@gmail.com>
+Namhyung Kim <namhyung@gmail.com>
+Nicolas FRANCOIS <nicolas.francois@centraliens.net>
+Paul E Condon <pecondon@mesanetworks.net>
+Peter Adkins <peter.adkins@kernelpicnic.net>
+Scot Doyle <lkml14@scotdoyle.com>
+Shawn Landden <shawn@churchofgit.com>
+Stéphane Aulery <saulery@free.fr>
+Stephen Smalley <sds@tycho.nsa.gov>
+Taisuke Yamada <tai@rakugaki.org>
+Torvald Riegel <triegel@redhat.com>
+Vincent Lefevre <vincent@vinc17.net>
+<ygrex@ygrex.ru>
+Yuri Kozlov <yuray@komyakino.ru>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+nptl.7
+ Michael Kerrisk
+ New page with details of the NPTL POSIX threads implementation
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+user_namespaces.7
+ Eric W. Biederman [Michael Kerrisk]
+ Document /proc/[pid]/setgroups
+
+
+Changes to individual pages
+---------------------------
+
+intro.1
+ Stéphane Aulery
+ Prompt is not % but $
+ Stéphane Aulery
+ Various improvements
+ - Add reference to other common shells dash(1), ksh(1)
+ - Add a reference to stdout(3)
+ - Separate cp and mv descriptions
+ - Add examples of special cases of cd
+ - Add su(1) and shutdown(8) references for section Logout
+ and poweroff
+ - Move Control-D to section Logout and poweroff
+ - Fix some little formatting errors
+ Stéphane Aulery
+ Add cross references cited
+ Stéphane Aulery
+ Order SEE ALSO section
+
+clone.2
+ Josh Triplett
+ Document that clone() silently ignores CLONE_PID and CLONE_STOPPED
+ Normally, system calls return EINVAL for flags they don't support.
+ Explicitly document that clone does *not* produce an error for
+ these two obsolete flags.
+ Michael Kerrisk
+ Small rewording of explanation of clone() wrt threads
+ Clone has so many effects that it's an oversimplification to say
+ that the *main* use of clone is to create a thread. (In fact,
+ the use of clone() to create new processes may well be more
+ common, since glibc's fork() is a wrapper that calls clone().)
+
+getgroups.2
+ Michael Kerrisk [Shawn Landden]
+ Add discussion of NPTL credential-changing mechanism
+ At the kernel level, credentials (UIDs and GIDs) are a per-thread
+ attribute. NPTL uses a signal-based mechanism to ensure that
+ when one thread changes its credentials, all other threads change
+ credentials to the same values. By this means, the NPTL
+ implementation conforms to the POSIX requirement that the threads
+ in a process share credentials.
+ Michael Kerrisk
+ ERRORS: add EPERM for the case where /proc/PID/setgroups is "deny"
+ Michael Kerrisk
+ Note capability associated with EPERM error for setgroups(2)
+ Michael Kerrisk
+ Refer reader to user_namespaces(7) for discussion of /proc/PID/setgroups
+ The discussion of /proc/PID/setgroups has moved from
+ proc(5) to user_namespaces(7).
+
+getpid.2
+ Michael Kerrisk
+ Note that getppid() returns 0 if parent is in different PID namespace
+
+getsockopt.2
+ Konstantin Shemyak
+ Note RETURN VALUE details when netfilter is involved
+
+ioctl_list.2
+ Heinrich Schuchardt
+ SEE ALSO ioctl_fat.2
+ Add FAT_IOCTL_GET_VOLUME_ID
+ SEE ALSO ioctl_fat.2
+ Heinrich Schuchardt
+ include/linux/ext2_fs.h
+ Include linux/ext2_fs.h does not contain any ioctl definitions
+ anymore.
+
+ Request codes EXT2_IOC* have been replaced by FS_IOC* in
+ linux/fs.h.
+
+ Some definitions of FS_IOC_* use long* but the actual code expects
+ int* (see fs/ext2/ioctl.c).
+
+msgop.2
+ Bill Pemberton
+ Remove EAGAIN as msgrcv() errno
+ The list of errnos for msgrcv() lists both EAGAIN and ENOMSG as
+ the errno for no message available with the IPC_NOWAIT flag.
+ ENOMSG is the errno that will be set.
+ Bill Pemberton
+ Add an example program
+
+open.2
+ Michael Kerrisk [Jason Vas Dias]
+ Mention blocking semantics for FIFO opens
+ See https://bugzilla.kernel.org/show_bug.cgi?id=95191
+
+seccomp.2
+ Jann Horn [Kees Cook, Mikael Pettersson, Andy Lutomirski]
+ Add note about alarm(2) not being sufficient to limit runtime
+ Jann Horn
+ Explain blacklisting problems, expand example
+ Michael Kerrisk [Kees Cook]
+ Add mention of libseccomp
+
+setgid.2
+ Michael Kerrisk
+ Clarify that setgid() changes all GIDs when caller has CAP_SETGID
+ Michael Kerrisk [Shawn Landden]
+ Add discussion of NPTL credential-changing mechanism
+ At the kernel level, credentials (UIDs and GIDs) are a per-thread
+ attribute. NPTL uses a signal-based mechanism to ensure that
+ when one thread changes its credentials, all other threads change
+ credentials to the same values. By this means, the NPTL
+ implementation conforms to the POSIX requirement that the threads
+ in a process share credentials.
+
+setresuid.2
+ Michael Kerrisk [Shawn Landden]
+ Add discussion of NPTL credential-changing mechanism
+ At the kernel level, credentials (UIDs and GIDs) are a per-thread
+ attribute. NPTL uses a signal-based mechanism to ensure that
+ when one thread changes its credentials, all other threads change
+ credentials to the same values. By this means, the NPTL
+ implementation conforms to the POSIX requirement that the threads
+ in a process share credentials.
+
+setreuid.2
+ Michael Kerrisk [Shawn Landden]
+ Add discussion of NPTL credential-changing mechanism
+ At the kernel level, credentials (UIDs and GIDs) are a per-thread
+ attribute. NPTL uses a signal-based mechanism to ensure that
+ when one thread changes its credentials, all other threads change
+ credentials to the same values. By this means, the NPTL
+ implementation conforms to the POSIX requirement that the threads
+ in a process share credentials.
+ Michael Kerrisk
+ SEE ALSO: add credentials(7)
+
+setuid.2
+ Michael Kerrisk
+ Clarify that setuid() changes all UIDs when caller has CAP_SETUID
+ Michael Kerrisk [Shawn Landden]
+ Add discussion of NPTL credential-changing mechanism
+ At the kernel level, credentials (UIDs and GIDs) are a per-thread
+ attribute. NPTL uses a signal-based mechanism to ensure that
+ when one thread changes its credentials, all other threads change
+ credentials to the same values. By this means, the NPTL
+ implementation conforms to the POSIX requirement that the threads
+ in a process share credentials.
+
+sigaction.2
+ Michael Kerrisk
+ Add discussion of rt_sigaction(2)
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc wrapper gives an EINVAL error on attempts to change the
+ disposition of either of the two real-time signals used by NPTL.
+
+sigpending.2
+ Michael Kerrisk
+ Add discussion of rt_sigpending(2)
+
+sigprocmask.2
+ Michael Kerrisk
+ Add discussion of rt_sigprocmask(2)
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc wrapper silently ignores attempts to block the two
+ real-time signals used by NPTL.
+
+sigreturn.2
+ Michael Kerrisk
+ Add discussion of rt_sigreturn(2)
+
+sigsuspend.2
+ Michael Kerrisk
+ Add discussion of rt_sigsuspend(2)
+
+sigwaitinfo.2
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc wrappers silently ignore attempts to wait for
+ signals used by NPTL.
+ Michael Kerrisk
+ Add discussion of rt_sigtimedwait(2)
+
+socket.2
+ Heinrich Schuchardt
+ SEE ALSO close(2)
+ The description mentions close(2). Hence it should also be
+ referenced in the SEE ALSO section.
+
+syscall.2
+ Jann Horn
+ Add x32 ABI
+
+umount.2
+ Eric W. Biederman
+ Document the effect of shared subtrees on umount(2)
+ Eric W. Biederman
+ Correct the description of MNT_DETACH
+ I recently realized that I had been reasoning improperly about
+ what umount(MNT_DETACH) did based on an insufficient description
+ in the umount.2 man page, that matched my intuition but not the
+ implementation.
+
+ When there are no submounts, MNT_DETACH is essentially harmless to
+ applications. Where there are submounts, MNT_DETACH changes what
+ is visible to applications using the detach directories.
+ Michael Kerrisk
+ Move "shared mount + umount" text to a subsection in NOTES
+
+aio_return.3
+ Stéphane Aulery
+ Document the return value on error
+ Reported by Alexander Holler <holler@ahsoftware.de>
+
+clock.3
+ Stéphane Aulery
+ CLOCKS_PER_SEC = 1000000 is required by XSI, not POSIX
+ Debian Bug #728213 reported by Tanaka Akira <akr@fsij.org>
+
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728213
+
+dlopen.3
+ Michael Kerrisk
+ Amend error in description of dlclose() behavior
+ The current text says that unloading depends on whether
+ the reference count falls to zero *and no other libraries
+ are using symbols in this library*. That latter text has
+ been there since man-pages-1.29, but it seems rather dubious.
+ How could the implementation know whether other libraries
+ are still using symbols in this library? Furthermore, no
+ other implementation's man page mentions this point.
+ Seems best to drop this point.
+ Michael Kerrisk
+ Add some details for RTLD_DEFAULT
+ Michael Kerrisk
+ Add some details on RTLD_NEXT and preloading
+ Michael Kerrisk
+ RTLD_NEXT works for symbols generally, not just functions
+ The common use case is for functions, but RTLD_NEXT
+ also applies to variable symbols.
+ Michael Kerrisk
+ dlclose() recursively closes dependent libraries
+ Note that dlclose() recursively closes dependent libraries
+ that were loaded by dlopen()
+ Michael Kerrisk
+ Rename second dlopen() argument from "flag" to "flags"
+ This is more consistent with other such arguments
+ Michael Kerrisk
+ Reformat text on RTLD_DEFAULT and RTLD_NEXT
+
+fmemopen.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+fpathconf.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The marking matches glibc marking.
+
+fputwc.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The marking matches glibc marking.
+
+fputws.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+fseek.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+fseeko.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+gcvt.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+getline.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The marking matches glibc marking.
+
+getwchar.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+hypot.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+iconv_open.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+if_nameindex.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The markings match glibc markings.
+
+initgroups.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+mq_open.3
+ Torvald Riegel
+ Add EINVAL error case for invalid name
+ This behavior is implementation-defined by POSIX. If the name
+ doesn't start with a '/', glibc returns EINVAL without attempting
+ the syscall.
+
+popen.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The marking matches glibc marking.
+
+pthread_kill.3
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc pthread_kill() function gives an error on attempts
+ to send either of the real-time signals used by NPTL.
+
+pthread_sigmask.3
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc implementation silently ignores attempts to block the two
+ real-time signals used by NPTL.
+
+pthread_sigqueue.3
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc pthread_sigqueue() function gives an error on attempts
+ to send either of the real-time signals used by NPTL.
+
+resolver.3
+ Stéphane Aulery [Jakub Wilk]
+ Document missing options used by _res structure indicate defaults
+ Missing options: RES_INSECURE1, RES_INSECURE2, RES_NOALIASES,
+ USE_INET6, ROTATE, NOCHECKNAME, RES_KEEPTSIG, BLAST, USEBSTRING,
+ NOIP6DOTINT, USE_EDNS0, SNGLKUP, SNGLKUPREOP, RES_USE_DNSSEC,
+ NOTLDQUERY, DEFAULT
+
+ Written from the glibc source and resolv.conf.5.
+
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527136
+ Stéphane Aulery
+ RES_IGNTC is implemented
+
+rint.3
+ Matt Turner
+ Document that halfway cases are rounded to even
+ Per IEEE-754 rounding rules.
+
+ The round(3) page describes the behavior of rint and nearbyint
+ in the halfway cases by saying:
+
+ These functions round x to the nearest integer, but round
+ halfway cases away from zero [...], instead of to the
+ nearest even integer like rint(3)
+
+sigqueue.3
+ Michael Kerrisk
+ NOTES: add "C library/kernel ABI differences" subheading
+ Michael Kerrisk
+ Clarify version info (mention rt_sigqueueinfo())
+
+sigsetops.3
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc sigfillset() function excludes the two real-time
+ signals used by NPTL.
+
+sigwait.3
+ Michael Kerrisk
+ Note treatment of signals used internally by NPTL
+ The glibc sigwait() silently ignore attempts to wait for
+ signals used by NPTL.
+
+strcoll.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The markings match glibc markings.
+
+strdup.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ The marking matches glibc marking.
+
+tzset.3
+ J William Piggott
+ Add 'std' quoting information
+
+ulimit.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+wcstombs.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+wctob.3
+ Ma Shimiao
+ ATTRIBUTES: Note function that is thread-safe
+ The marking matches glibc marking.
+
+xdr.3
+ Taisuke Yamada
+ Clarified incompatibility and correct usage of XDR API
+ See http://bugs.debian.org/628099
+
+console_codes.4
+ Scot Doyle
+ Add Console Private CSI sequence 15
+ An undocumented escape sequence in drivers/tty/vt/vt.c brings the
+ previously accessed virtual terminal to the foreground.
+ mtk: Patch misattributed to Taisuke Yamada in Git commit
+ because of a muck up on my part.
+ Michael Kerrisk
+ Add kernel version number for CSI sequence 15
+
+random.4
+ Michael Kerrisk
+ Fix permissions shown for the devices
+ These days, the devices are RW for everyone.
+
+filesystems.5
+ Michael Kerrisk
+ Remove dubious claim about comparative performance of ext2
+ Perhaps it was the best filesystem performance-wise in
+ the 20th century, when that text was written. That probably
+ ceased to be true quite a long time ago, though.
+ Stéphane Aulery
+ Add cross references for ext filesystems
+ Stéphane Aulery
+ Specifies the scope of this list and its limits.
+
+host.conf.5
+hosts.5
+resolv.conf.5
+ Stéphane Aulery [Paul E Condon]
+ Cross references of these pages.
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298259
+
+host.conf.5
+ Stéphane Aulery
+ Rework discussion of nospoof, spoofalert, spoof and RESOLV_SPOOF_CHECK
+ The keywords and environment variables "nospoof", "spoofalert",
+ "spoof" and RESOLV_SPOOF_CHECK were added to glibc 2.0.7 but
+ never implemented
+
+ Move descriptions to historical section and reorder it for clarity
+
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773443
+
+hosts.5
+ Stéphane Aulery [Vincent Lefevre]
+ Mention 127.0.1.1 for FQDN and IPv6 examples
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562890
+
+proc.5
+ Taisuke Yamada
+ Document /proc/PID/status VmPin field
+ See https://bugs.launchpad.net/bugs/1071746
+ Michael Kerrisk
+ Document (the obsolete) /proc/PID/seccomp
+ Michael Kerrisk
+ Replace description of 'uid_map' with a reference to user_namespaces(7)
+ All of the information in proc(5) was also present in
+ user_namespaces(7), but the latter was more detailed
+ and up to date.
+ Taisuke Yamada
+ Fix SELinux /proc/pid/attr/current example
+ Since the /proc/pid/attr API was added to the kernel, there
+ have been a couple of changes to the SELinux handling of
+ /proc/pid/attr/current. Fix the SELinux /proc/pid/attr/current
+ example text to reflect these changes and note which kernel
+ versions first included the changes.
+
+securetty.5
+ Stéphane Aulery [Nicolas FRANCOIS]
+ Note that the pam_securetty module also uses this file
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528015
+
+ This patch is a modified version of the one proposed without
+ parts specific to Debian.
+
+boot.7
+ Michael Witten
+ Copy edit
+ While a lot of the changes are issues of presentation,
+ there are also issues of grammar and punctuation.
+ Michael Witten
+ Mention `systemd(1)' and its related `bootup(7)'
+ It's important that the reader receive contemporary information.
+
+credentials.7
+ Michael Kerrisk
+ SEE ALSO: add pthreads(7)
+ Michael Kerrisk
+ Add reference to nptl(7)
+
+feature_test_macros.7
+ Michael Kerrisk
+ Update discussion of _FORTIFY_SOURCE
+ Since the initial implementation a lot more checks were added.
+ Describe all the checks would be too verbose (and would soon
+ fall out of date as more checks are added). So instead, describe
+ the kinds of checks that are done more generally.
+ Also a few other minor edits to the text.
+
+hier.7
+ Stéphane Aulery
+ First patch of a series to achieve compliance with FHS 2.3
+ Stéphane Aulery
+ SGML and XML directories are separated in FHS 2.3
+ Stéphane Aulery
+ Add missing directories defined by FHS 2.3
+ Stéphane Aulery
+ Identify which directories are optional
+ Stéphane Aulery
+ Document /initrd, /lost+found and /sys
+ Ubuntu Bug #70094 reported by Brian Beck
+ https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/70094
+ Stéphane Aulery
+ Explain YP, which is not obvious
+
+ipv6.7
+ Stéphane Aulery [David Madore]
+ SOL_IPV6 and other SOL_* options socket are not portable
+ See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472447
+
+man-pages.7
+ Michael Kerrisk [Bill Pemberton]
+ Add indent(1) command that produces desired formatting for example code
+ Stéphane Aulery
+ Improve description of sections in accordance with intro pages
+
+packet.7
+ Michael Kerrisk
+ Rework description of fanout algorithms as list
+ Michael Kerrisk
+ Remove mention of needing UID 0 to create packet socket
+ The existing text makes no sense. The check is based
+ purely on a capability check. (Kernel function
+ net/packet/af_packet.c::packet_create()
+ Michael Kerrisk
+ Remove text about ancient glibc not defining SOL_PACKET
+ This was fixed in glibc 2.1.1, which is a long while ago.
+ And in any case, there is nothing special about this case;
+ it's just one of those times when glibc lags.
+ Michael Kerrisk
+ Rework description of 'sockaddr_ll' fields as a list
+ Michael Kerrisk
+ Various minor edits
+
+pthreads.7
+ Michael Kerrisk
+ Add references to nptl(7)
+
+raw.7
+ Michael Kerrisk
+ Rephrase "Linux 2.2" language to "Linux 2.2 or later"
+ The man page was written in the LInux 2.2 timeframe, and
+ some phrasing was not future-proof.
+
+signal.7
+ Michael Kerrisk
+ Note when Linux added realtime signals
+ Michael Kerrisk
+ Correct the range of realtime signals
+ Michael Kerrisk
+ Summarize 2.2 system call changes that resulted from larger signal sets
+ Michael Kerrisk
+ SEE ALSO: add nptl(7)
+
+tcp.7
+ Peter Adkins
+ Document removal of TCP_SYNQ_HSIZE
+ Looking over the man page for 'tcp' I came across a reference to
+ tuning the 'TCP_SYNQ_HSIZE' parameter when increasing
+ 'tcp_max_syn_backlog' above 1024. However, this static sizing was
+ removed back in Linux 2.6.20 in favor of dynamic scaling - as
+ part of commit 72a3effaf633bcae9034b7e176bdbd78d64a71db.
+
+user_namespaces.7
+ Eric W. Biederman
+ Update the documentation to reflect the fixes for negative groups
+ Files with access permissions such as rwx---rwx give fewer
+ permissions to their group then they do to everyone else. Which
+ means dropping groups with setgroups(0, NULL) actually grants a
+ process privileges.
+
+ The unprivileged setting of gid_map turned out not to be safe
+ after this change. Privileged setting of gid_map can be
+ interpreted as meaning yes it is ok to drop groups. [ Eric
+ additionally noted: Setting of gid_map with privilege has been
+ clarified to mean that dropping groups is ok. This allows
+ existing programs that set gid_map with privilege to work
+ without changes. That is, newgidmap(1) continues to work
+ unchanged.]
+
+ To prevent this problem and future problems, user namespaces were
+ changed in such a way as to guarantee a user can not obtain
+ credentials without privilege that they could not obtain without
+ the help of user namespaces.
+
+ This meant testing the effective user ID and not the filesystem
+ user ID, as setresuid(2) and setregid(2) allow setting any process
+ UID or GID (except the supplementary groups) to the effective ID.
+
+ Furthermore, to preserve in some form the useful applications
+ that have been setting gid_map without privilege, the file
+ /proc/[pid]/setgroups was added to allow disabling setgroups(2).
+ With setgroups(2) permanently disabled in a user namespace, it
+ again becomes safe to allow writes to gid_map without privilege.
+ Michael Kerrisk
+ Rework some text describing permission rules for updating map files
+ No (intentional) change to the facts, but this restructuring
+ should make the meaning easier to grasp.
+ Michael Kerrisk
+ Update kernel version associated with 5-line limit for map files
+ As at Linux 3.18, the limit is still five lines, so mention the
+ more recent kernel version in the text.
+ Michael Kerrisk [Alban Crequy]
+ Handle /proc/PID/setgroups in the example program
+ Michael Kerrisk
+ Rework text describing restrictions on updating /proc/PID/setgroups
+ No (intentional) changes to factual description, but the
+ restructured text is hopefully easier to grasp.
+ Michael Kerrisk
+ Explain why the /proc/PID/setgroups file was added
+
+ldconfig.8
+ Michael Kerrisk
+ Note use of /lib64 and /usr/lib64 on some 64-bit architectures
+
+ld.so.8
+ Michael Kerrisk
+ Note the use of /lib64 and /usr/lib64 on some 64-bit architectures
+
+
+
+==================== Changes in man-pages-3.83 ====================
+
+Released: 2015-04-19, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Andreas Baak <andreas.baak@gmail.com>
+Andreas Dilger <adilger@dilger.ca>
+cdlscpmv <cdlscpmv@gmail.com>
+Cyrill Gorcunov <gorcunov@openvz.org>
+Darrick J. Wong <darrick.wong@oracle.com>
+David Rientjes <rientjes@google.com>
+Dima Tisnek <dimaqq@gmail.com>
+Eric Sandeen <sandeen@redhat.com>
+Fabien Pichot <fpichot@bouledef.eu>
+Felix Sedlmeier <sedlmeier@gmx.de>
+Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Jann Horn <jann@thejh.net>
+Jon Grant <jg@jguk.org>
+Jonny Grant <jg@jguk.org>
+Kees Cook <keescook@chromium.org>
+Masanari Iida <standby24x7@gmail.com>
+Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Nikos Mavrogiannopoulos <nmav@gnutls.org>
+Omar Sandoval <osandov@osandov.com>
+Pierre Chifflier <pollux@debian.org>
+Robin H. Johnson <robbat2@gentoo.org>
+Rob Landley <rob@landley.net>
+Theodore Ts'o <tytso@mit.edu>
+Vlastimil Babka <vbabka@suse.cz>
+Walter Harms <wharms@bfs.de>
+William Woodruff <william@tuffbizz.com>
+YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>
+Zeng Linggang <zenglg.jy@cn.fujitsu.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+posix_madvise.3
+ Michael Kerrisk
+ New page documenting posix_madvise(3)
+
+ftw.3
+ Michael Kerrisk
+ Reorganize the page to give primacy to nftw()
+ nftw() is the better API, and POSIX.1-2008 marks ftw() obsolete.
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+getdents.2
+ Michael Kerrisk [Dima Tisnek]
+ Document getdents64()
+ See https://bugzilla.kernel.org/show_bug.cgi?id=14795
+
+mount.2
+ Michael Kerrisk, Theodore Ts'o [Eric Sandeen, Andreas Dilger,
+ Omar Sandoval, Darrick J. Wong]
+ Document MS_LAZYTIME
+
+proc.5
+ Michael Kerrisk
+ Document /proc/sys/kernel/randomize_va_space
+ Michael Kerrisk
+ Document /proc/PID/fdinfo epoll format
+ Michael Kerrisk
+ Describe /proc/PID/fdinfo eventfd format
+ Michael Kerrisk
+ Document /proc/PID/fdinfo signalfd format
+
+
+New and changed links
+---------------------
+
+newfstatat.2
+ Michael Kerrisk
+ New link to fstatat64.2
+
+prlimit64.2
+ Michael Kerrisk
+ New link to getrlimit.2
+
+
+Global changes
+--------------
+
+Various section 3 math pages
+ Michael Kerrisk
+ Note that these functions are also in POSIX.1-2001 and POSIX.1-2008
+
+
+Changes to individual pages
+---------------------------
+
+getent.1
+ Robin H. Johnson
+ Document options
+ The options to getent are now documented, after being around for
+ nearly a decade without changes.
+ Michael Kerrisk
+ Document help and version options
+
+fallocate.2
+ Michael Kerrisk
+ Fix kernel version number for FALLOC_FL_ZERO_RANGE
+ FALLOC_FL_ZERO_RANGE was added in 3.15, not 3.14.
+ Michael Kerrisk
+ Note that SMB3 added FALLOC_FL_ZERO_RANGE support in Linux 3.17
+
+getrlimit.2
+ Michael Kerrisk
+ Note that the underlying system call for prlimit() is prlimit64()
+ Michael Kerrisk
+ Remove "_FILE_OFFSET_BITS == 64" from prlimit() FTM requirements
+ "_FILE_OFFSET_BITS == 64" is not needed to get the prlimit()
+ declaration.
+
+ioctl_list.2
+ Nikos Mavrogiannopoulos
+ SIOCADDRT accepts in6_rtmsg in INET6 protocol
+ Heinrich Schuchardt
+ TFD_IOC_SET_TICKS
+ timerfd_create.2 mentions TFD_IOC_SET_TICKS. We should add it to
+ ioctl_list.2, too.
+
+llseek.2
+ Michael Kerrisk
+ Advise reader to use lseek(2) instead
+ Michael Kerrisk
+ llseek() exists on 32-bit platforms to support seeking to large offsets
+
+madvise.2
+ David Rientjes
+ Specify MADV_REMOVE returns EINVAL for hugetlbfs
+ madvise(2) actually returns with error EINVAL for MADV_REMOVE
+ when used for hugetlb VMAs, not EOPNOTSUPP, and this has been
+ the case since MADV_REMOVE was introduced in commit f6b3ec238d12
+ ("madvise(MADV_REMOVE): remove pages from tmpfs shm backing
+ store"). Specify the exact behavior.
+ Michael Kerrisk
+ SEE ALSO: add posix_madvise(2)
+
+poll.2
+ Michael Kerrisk [Andreas Baak]
+ SEE ALSO: add epoll(7)
+
+posix_fadvise.2
+ Michael Kerrisk
+ Add "C library/kernel ABI differences" subsection
+
+pread.2
+ Michael Kerrisk
+ Add "C library/kernel ABI differences" subsection
+
+seccomp.2
+ Michael Kerrisk [Pierre Chifflier, Kees Cook]
+ Note that seccomp_data is read-only
+
+stat.2
+ Michael Kerrisk
+ Add some details on various "stat" versions
+ Three versions of "stat" appeared on 32-bit systems,
+ dealing with structures of different (increasing) sizes.
+ Explain some of the details, and also note that the
+ situation is simpler on modern 64-bit architectures.
+ Michael Kerrisk
+ Add mention of newfstatat()
+ The underlying system call for fstatat() is newfstatat()
+ on some architectures.
+
+symlink.2
+ Michael Kerrisk [Jonny Grant]
+ ERRORS: add linkpath=="" case for ENOENT
+
+syscalls.2
+ Michael Kerrisk
+ Remove prlimit()
+ There really is only the prlimit64() system call.
+ Michael Kerrisk
+ Add some details about the "multiple versions of system calls"
+ The multiple-system-call-version phenomenon is particularly a
+ feature of older 32-bit platforms. Hint at that fact in the text.
+
+timerfd_create.2
+ Cyrill Gorcunov [Michael Kerrisk]
+ Document TFD_IOC_SET_TICKS ioctl() operation
+ Michael Kerrisk
+ Add some details to C library/kernel ABI differences
+
+unshare.2
+ Michael Kerrisk [Fabien Pichot]
+ Remove mention of "System V" from discussion of CLONE_NEWIPC
+ These days, CLONE_NEWIPC also affects POSIX message queues.
+
+asprintf.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+carg.3
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+ccos.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+ccosh.3
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+cexp.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+
+clock.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that is thread-safe
+
+clog.3
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+csin.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+csinh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+csqrt.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Simplify description of what these functions calculate
+
+ctan.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+ctanh.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Add introductory sentence explaining what these functions calculate
+
+ctime.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+exec.3
+ Michael Kerrisk
+ SYNOPSIS: Clarify calling signature for execl() and execlp()
+ Michael Kerrisk [Andreas Baak]
+ Correct prototype for execle()
+ Make the prototype shown into correct C.
+
+ftw.3
+ Michael Kerrisk [Felix Sedlmeier]
+ ftw() and nftw() differ for the non-stat-able symlink case
+ The POSIX specification of ftw() says that an un-stat-able
+ symlink may yield either FTW_NS or FTW_SL. The specification
+ of nftw() does not carry this statement.
+ Michael Kerrisk
+ CONFORMING TO: add POSIX.1-2008
+ Michael Kerrisk
+ Update POSIX version references in NOTES
+
+getcwd.3
+ Jann Horn [Michael Kerrisk]
+ Note behavior for unreachable current working directory
+ Michael Kerrisk
+ Add ENOMEM error
+
+gethostbyname.3
+ Michael Kerrisk [Jonny Grant]
+ Clarify that NO_ADDRESS and NO_DATA are synonyms
+ Michael Kerrisk
+ Add some detail for NO_DATA
+ Text consistent with POSIX and FreeBSD's gethostbyname() man page.
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+getnetent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+get_nprocs_conf.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getutent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+glob.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+insque.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+
+login.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+lseek64.3
+ Michael Kerrisk
+ Clarify details with respect to 32-bit and 64-bit systems
+
+malloc.3
+ Michael Kerrisk
+ Add ENOMEM error
+
+mbsnrtowcs.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+mbsrtowcs.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+mq_notify.3
+ Michael Kerrisk
+ Add "C library/kernel ABI differences" subsection
+
+mq_open.3
+ Michael Kerrisk [Fabien Pichot]
+ NOTES: explain differences from the underlying system call
+ The check for the slash at the start of a pathname is done in glibc
+
+openpty.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+perror.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+posix_memalign.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+printf.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+ Walter Harms [Michael Kerrisk]
+ Simplify the example code
+
+qsort.3
+ Michael Kerrisk [Rob Landley]
+ alphasort() and versionsort() are not suitable for 'compar'
+ In glibc 2.10, the prototypes of alphasort() and versionsort()
+ were changed so that the arguments switched from 'const void *' to
+ 'const struct dirent **', to match the POSIX.1-2008 specification
+ of alphasort(). As such, compiler warnings will result if
+ these functions are used as the arguments of qsort().
+
+ warning: passing argument 4 of 'qsort' from incompatible
+ pointer type
+ expected '__compar_fn_t' but argument is of type
+ 'int (*)(const struct dirent **, const struct dirent **)'
+
+ Therefore, remove the ancient NOTES text suggesting that
+ alphasort() and versionsort() can be used as suitable
+ 'compar' arguments for qsort().
+
+realpath.3
+ Michael Kerrisk [Jon Grant]
+ Add ENOMEM error
+
+scandir.3
+ Michael Kerrisk
+ glibc 2.10 changed the argument types for alphasort() and versionsort()
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+scanf.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+setnetgrent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+significand.3
+ Ma Shimiao
+ ATTRIBUTES: Note functions that are thread-safe
+
+strcasecmp.3
+ Michael Kerrisk [Jonny Grant]
+ Clarify that strcasecmp() does a byte-wise comparison
+ Michael Kerrisk
+ CONFORMING TO: add POSIX.1-2008
+
+unlocked_stdio.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+updwtmp.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+wcrtomb.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+wcsnrtombs.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+wcsrtombs.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+wordexp.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+wprintf.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+proc.5
+ Michael Kerrisk
+ Describe "mnt_id" field of /proc/PID/fdinfo
+ Michael Kerrisk
+ Note that abstract sockets are included in /proc/net/unix
+ Michael Kerrisk
+ Update description /proc/sys/unix 'Type' field
+ The existing text was very crufty. UNIX domain sockets
+ support more than SOCK_STREAM for a _very_ long time now.
+ Michael Kerrisk
+ Add some detail to /proc/PID/timers
+ Michael Kerrisk [Vlastimil Babka]
+ Enhance discussion of /proc/PID/status 'VmSwap' field
+
+epoll.7
+ Michael Kerrisk
+ SEE ALSO: add poll(2) and select(2)
+
+icmp.7
+ YOSHIFUJI Hideaki/吉藤英明
+ Document net.ipv4.ping_group_range knob
+
+nptl.7
+ Michael Kerrisk
+ Add reference to timer_create(2)
+
+
+==================== Changes in man-pages-4.00 ====================
+
+Released: 2015-05-07, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Advait Dixi <advaitdixit@hotmail.com>
+Alain Kalker <a.c.kalker@gmail.com>
+Andi Kleen <andi@firstfloor.org>
+Andreas Gruenbacher <agruenba@redhat.com>
+Andreas Heiduk <asheiduk@googlemail.com>
+Askar Safin <safinaskar@mail.ru>
+Brice Goglin <Brice.Goglin@inria.fr>
+Cameron Norman <camerontnorman@gmail.com>
+Carlos O'Donell <carlos@redhat.com>
+Chris Metcalf <cmetcalf@tilera.com>
+Christophe Lohr <Christophe.Lohr@telecom-bretagne.eu>
+Christopher Head <chead@chead.ca>
+Christoph Hellwig <hch@infradead.org>
+David Wilcox <davidvsthegiant@gmail.com>
+Denis Du <denisdu@ruggedcom.com>
+Egmont Koblinger <egmont@gmail.com>
+Filipe Brandenburger <filbranden@gmail.com>
+Filipus Klutiero <chealer@gmail.com>
+Florian Weimer <fweimer@redhat.com>
+Frédéric Maria <frederic.maria@free.fr>
+Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
+Graham Shaw <gdshaw@riscpkg.org>
+Gregor Jasny <igjasny@googlemail.com>
+Guillem Jover <guillem@hadrons.org>
+Guy Harris <guy@alum.mit.edu>
+Heinrich Schuchardt <xypron.glpk@gmx.de>
+Ian Pilcher <arequipeno@gmail.com>
+Jann Horn <jann@thejh.net>
+Jason Newton <nevion@gmail.com>
+J. Bruce Fields <bfields@fieldses.org>
+Jiri Pirko <jpirko@redhat.com>
+Joachim Wuttke <j.wuttke@fz-juelich.de>
+Joern Heissler <contact@joern.heissler.de>
+Jonathan Nieder <jrnieder@gmail.com>
+Joonas Salo <salo.joonas@gmail.com>
+Jussi Lehtola <jussilehtola@fedoraproject.org>
+Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
+KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
+Laurence Gonsalves <laurence@xenomachina.com>
+Magnus REFTEL <magnus.xm.reftel@stericsson.com>
+Michael Kerrisk <mtk.manpages@gmail.com>
+NeilBrown <neilb@suse.de>
+Regid Ichira <regid23@nt1.in>
+Sam Varshavchik <mrsam@courier-mta.com>
+Steinar H. Gunderson <sgunderson@bigfoot.com>
+Stéphane Aulery <saulery@free.fr>
+Stephane Fillod <fillods@users.sf.net>
+Tetsuo Handa <from-linux-kernel@i-love.sakura.ne.jp>
+Thomas Hood <jdthood@gmail.com>
+Urs Thuermann <urs@isnogud.escape.de>
+Vasiliy Kulikov <segooon@gmail.com>
+Vegard Nossum <vegard.nossum@gmail.com>
+Weijie Yang <weijie.yang@samsung.com>
+William Woodruff <william@tuffbizz.com>
+Zeng Linggang <zenglg.jy@cn.fujitsu.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+get_phys_pages.3
+ William Woodruff
+ Document get_phys_pages() and get_avphys_pages()
+
+loop.4
+ Urs Thuermann, Michael Kerrisk
+ New page documenting the loop device
+
+xattr.7
+ Andreas Gruenbacher
+ Import attr(5) man page from the 'attr' project
+ After discussions with Andreas Gruenbacher, it makes sense to
+ move this page into man-pages, since it mostly relates to
+ kernel details. Since this is an overview page,
+ we'll move it to Section 7.
+ Michael Kerrisk
+ Rename page
+ "xattr" is a more meaningful name than "attr" (it resonates
+ with the names of the system calls), so as long as we are
+ moving the page to a new section, we'll change the name as well,
+ and retain an acl(5) link so that old references remain valid.
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+mmap.2
+ Michael Kerrisk [Andi Kleen]
+ Document MAP_HUGE_2MB, MAP_HUGE_1GB, and MAP_HUGE_SHIFT
+
+shmget.2
+ Michael Kerrisk [Andi Kleen]
+ Document SHM_HUGE_2MB, SHM_HUGE_1GB, and SHM_HUGE_SHIFT
+
+resolver.3
+ Michael Kerrisk [Jonathan Nieder]
+ Add descriptions of some other resolver functions
+ Add res_ninit(), res_nquery(), res_nsearch(),
+ and res_nquerydomain(), res_nmkquery(), res_nsend().
+
+tty_ioctl.4
+ Frédéric Maria [Stephane Fillod, Andreas Heiduk]
+ Document TIOCMIWAIT and TIOCGICOUNT
+ Michael Kerrisk
+ Document TIOCGEXCL
+ Michael Kerrisk
+ Document TIOGCPKT
+ Michael Kerrisk
+ Document TIOCSPTLCK
+ Michael Kerrisk
+ Document TIOCGPTLCK
+
+
+New and changed links
+---------------------
+
+CMSG_DATA.3
+ Michael Kerrisk
+ New link to cmsg(3)
+
+CMSG_LEN.3
+ Michael Kerrisk
+ New link to cmsg(3)
+
+dprintf.3
+ Michael Kerrisk
+ Convert to a link to printf.3
+
+get_avphys_pages.3
+ William Woodruff
+ New link to new get_phys_pages.3 page
+
+res_ninit.3
+res_nmkquery.3
+res_nquery.3
+res_nquerydomain.3
+res_nsearch.3
+res_nsend.3
+ Michael Kerrisk
+ New links to resolver(3) man page
+
+loop-control.4
+ Michael Kerrisk
+ New link to loop.4
+
+attr.5
+ Michael Kerrisk
+ New link to xattr(7)
+
+
+Global changes
+--------------
+
+chown.2
+execve.2
+prctl.2
+truncate.2
+proc.5
+capabilities.7
+ld.so.8
+ Michael Kerrisk
+ Tighter wording: 'mode bit' rather than 'permission bit'
+ For sticky, set-UID, and set-GID mode bits (as used in POSIX).
+
+
+Changes to individual pages
+---------------------------
+
+add_key.2
+keyctl.2
+request_key.2
+ Michael Kerrisk
+ SEE ALSO: add keyrings(7)
+
+add_key.2
+request_key.2
+ Michael Kerrisk
+ SEE ALSO: add keyctl(3)
+
+epoll_ctl.2
+ Michael Kerrisk
+ After EPOLLHUP, EOF will be seen only after all data has been consumed
+
+epoll_wait.2
+ Michael Kerrisk
+ Clarify that signal mask treatment in epoll_pwait() is per-thread
+ s/sigprocmask()/pthread_sigmask()/
+
+fcntl.2
+ Michael Kerrisk [Vegard Nossum]
+ Note an F_SETSIG corner case
+
+get_mempolicy.2, set_mempolicy
+ Brice Goglin
+ Policy is per thread, not per process
+
+getxattr.2
+listxattr.2
+removexattr.2
+setxattr.2
+capabilities.7
+ Michael Kerrisk
+ Adjust "attr(5)" references to "xattr(7)"
+
+ioctl.2
+ Michael Kerrisk
+ SEE ALSO: add console_ioctl(2) and tty_ioctl(2)
+
+listxattr.2
+xattr.7
+ Michael Kerrisk
+ Describe listxattr(2) E2BIG error and document it as a BUG
+
+mkdir.2
+ Michael Kerrisk
+ Wording fixes + point reader at stat(2) for explanation of file mode
+ Michael Kerrisk [Andreas Grünbacher]
+ Further tweaks to text on S_ISVTX and 'mode' argument
+
+mknod.2
+ Michael Kerrisk
+ Rewordings + point reader at stat(2) for details of mode bits
+
+mmap.2
+ Michael Kerrisk
+ Remove text that implies that munmap() syncs MAP_SHARED mapping to file
+ The existing text in this page:
+
+ MAP_SHARED Share this mapping. Updates to the mapping
+ are visible to other processes that map this
+ file, and are carried through to the underly‐
+ ing file. The file may not actually be
+ updated until msync(2) or munmap() is called.
+
+ implies that munmap() will sync the mapping to the underlying
+ file. POSIX doesn't require this, and some light reading of the
+ code and some light testing (fsync() after munmap() of a large
+ file) also indicates that Linux doesn't do this.
+
+msync.2
+ Michael Kerrisk
+ Rework text of DESCRIPTION
+ Rewrite the text somewhat, for easier comprehension.
+ No (intentional) changes to factual content
+
+nfsservctl.2
+ Michael Kerrisk [J. Bruce Fields]
+ Note that nfsservctl() was replaced by files in nfsd filesystem
+
+open.2
+ Michael Kerrisk [Andreas Gruenbacher]
+ open() honors the S_ISVTX, S_ISUID, and S_ISGID bits in 'mode'
+ Michael Kerrisk
+ Tighten wording: use 'mode bit' rather than 'permission bit'
+ Michael Kerrisk [NeilBrown]
+ BUGS: O_CREAT | O_DIRECTORY succeeds if pathname does not exist
+
+poll.2
+ Michael Kerrisk [Ian Pilcher]
+ Clarify that signal mask treatment in ppoll() is per-thread
+ s/sigprocmask()/pthread_sigmask()/
+ Michael Kerrisk [Sam Varshavchik]
+ After POLLHUP, EOF will be seen only after all data has been consumed
+ Michael Kerrisk
+ Make it clearer which bits are ignored in 'events'
+
+prctl.2
+ Michael Kerrisk [David Wilcox, Filipe Brandenburger]
+ Note that "parent" for purposes of PR_SET_DEATHSIG is a *thread*
+ See https://bugzilla.kernel.org/show_bug.cgi?id=43300
+
+sendfile.2
+ Michael Kerrisk [Jason Newton]
+ Note that sendfile does not support O_APPEND for 'out_fd'
+ See https://bugzilla.kernel.org/show_bug.cgi?id=82841
+ Michael Kerrisk [Gregor Jasny]
+ RETURN VALUE: note the possibility of "short sends"
+ See https://bugzilla.kernel.org/show_bug.cgi?id=97491
+ Michael Kerrisk [Askar Safin]
+ Clarify text on 'out_fd' and regular files in Linux 2.4
+ See https://bugzilla.kernel.org/show_bug.cgi?id=86001
+
+shutdown.2
+ Michael Kerrisk [Stéphane Aulery]
+ BUGS: UNIX domain sockets now detect invalid 'how' values
+ Bug fixed in Linux 3.7.
+ See https://bugzilla.kernel.org/show_bug.cgi?id=47111
+
+sigaction.2
+ Michael Kerrisk
+ Refer the reader to fcntl(2) F_SETSIG for further details on si_fd
+
+stat.2
+ Jann Horn
+ Add note about stat() being racy
+ Andreas Gruenbacher
+ Improve description of some mode constants
+ Michael Kerrisk [Andreas Grünbacher]
+ Remove excessive leading zeros on some constants
+ Michael Kerrisk
+ Add text on POSIX terms "file mode bits" and "file permission bits"
+ Recent changes to various pages employ this distinction.
+ Michael Kerrisk
+ Tighten wording: use 'mode bit' rather than 'permission bit'
+ According to POSIX, the the 9 UGO*RWX bits are permissions, and
+ 'mode' is used to refer to collectively to those bits plus sticky,
+ set-UID, and set_GID bits.
+
+syslog.2
+ Michael Kerrisk
+ SEE ALSO: add dmesg(1)
+
+umask.2
+open.2
+mknod.2
+mkdir.2
+ Andreas Gruenbacher
+ Explain what default ACLs do
+ Explain the effect that default ACLs have (instead of the umask)
+ in umask.2. Mention that default ACLs can have an affect in
+ open.2, mknod.2, and mkdir.2.
+
+unshare.2
+ Michael Kerrisk [Florian Weimer]
+ Give the reader a hint that unshare() works on processes or threads
+ See https://bugzilla.kernel.org/show_bug.cgi?id=59281
+
+atexit.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+bsearch.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+cmsg.3
+ Michael Kerrisk [Christopher Head]
+ Fix error in SCM_RIGHTS code sample
+ Remove erroneous second initialization of msg.msg_controllen
+ in the example code for SCM_RIGHTS.
+ See https://bugzilla.kernel.org/show_bug.cgi?id=15952
+
+CPU_SET.3
+ Chris Metcalf
+ Clarify language about "available" cpus
+ The CPU_SET.3 man page uses the adjective "available" when
+ explaining what the argument to CPU_SET() means. This is
+ confusing, since "available" isn't well-defined. The kernel
+ has a set of adjectives (possible, present, online, and active)
+ that qualify cpus, but normally none of these are what the
+ cpu_set_t bit index means: it's just "which cpu", using the
+ kernel's internal numbering system, even if that cpu isn't
+ possible or present.
+
+ This change removes the word "available" and adds a sentence
+ warning that cpu sets may not be contiguous due to dynamic
+ cpu hotplug, etc.
+
+err.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+ftw.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+gethostbyname.3
+ Carlos O'Donell
+ NSS plugins searched first
+ Carlos O'Donell
+ "order" is obsolete
+
+gethostid.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+getmntent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+get_nprocs_conf.3
+ Michael Kerrisk
+ Use exit() rather than return in main()
+
+getopt.3
+ Michael Kerrisk [Guy Harris]
+ Remove crufty BUGS section
+ See https://bugzilla.kernel.org/show_bug.cgi?id=90261
+
+iconv_close.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+inet_ntop.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+longjmp.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+lsearch.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+mcheck.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+on_exit.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+printf.3
+ Michael Kerrisk [Egmont Koblinger]
+ Merge dprintf() and vdprintf() discussion into this page
+ Michael Kerrisk
+ SEE ALSO: add puts(3)
+ Michael Kerrisk
+ Move return value discussion to proper RETURN VALUE section
+
+putpwent.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+qsort.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+regex.3
+ Michael Kerrisk [Laurence Gonsalves]
+ Fix error in description of 'cflags'
+ 'cflags' is a bit mask of *zero* (not one) or more flags.
+
+resolver.3
+ Stéphane Aulery
+ Add info about RES_INSECURE1 and RES_INSECURE2 option in debug mode
+
+scanf.3
+ Joern Heissler
+ Improve description of %n specifier
+
+setjmp.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+setlocale.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+setlogmask.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+sleep.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+strsignal.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that isn't thread-safe
+
+sysconf.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+undocumented.3
+ William Woodruff
+ Remove documented functions
+
+tty_ioctl.4
+ Michael Kerrisk [Denis Du]
+ Fix error in code example
+
+proc.5
+ Michael Kerrisk [Cameron Norman, Vasiliy Kulikov]
+ Document /proc mount options
+ Document the 'hidepid' and 'gid' mount options that were added in
+ Linux 3.3. See https://bugzilla.kernel.org/show_bug.cgi?id=90641
+ Based on text by Vasiliy Kulikov in
+ Documentation/filesystems/proc.txt.
+ Michael Kerrisk [Kirill A. Shutemov]
+ Improve description of /proc/PID/status
+ Guillem Jover
+ Document /proc/PID/exe behaviour on unlinked pathnames
+ Michael Kerrisk [Weijie Yang]
+ Document /proc/PID/status VmPMD
+
+resolv.conf.5
+ Stéphane Aulery [Thomas Hood]
+ Document use-vc option added to glibc 2.14
+ Fix Ubuntu bug #1110781:
+ https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1110781
+ Stéphane Aulery [Thomas Hood]
+ Document RES_SNGLKUPREOP
+ Fix Ubuntu bug #1110781:
+ https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1110781
+
+tzfile.5
+ Sam Varshavchik
+ Add various details on version 2 format
+
+aio.7
+ Michael Kerrisk
+ Add details and update URL for OLS 2003 paper on AIO
+
+bootparam.7
+ Michael Kerrisk [Alain Kalker]
+ Update discussion of 'debug' option
+ See https://bugzilla.kernel.org/show_bug.cgi?id=97161
+ Michael Kerrisk
+ Summary of multiple changes: remove cruft from this page.
+ Much of the detail on hardware specifics in this page dates
+ from the 20th century. (The last major update to this page was in
+ man-pages-1.14!) It's hugely out of date now (many of these
+ devices disappeared from the kernel years ago.) So, I've taken
+ a large scythe to the page to remove anything that looks
+ seriously dated. In the process, the page has shrunk to less
+ than 50% of its previous size.
+ Michael Kerrisk
+ Remove "buff=" details
+ This seems to have gone away in Linux 2.2.
+ Michael Kerrisk
+ Remove crufty "Mouse drivers" options
+ Michael Kerrisk
+ Remove crufty "General non-device-specific boot arguments" options
+ Michael Kerrisk
+ Remove crufty "Hard disks" options
+ Michael Kerrisk
+ Remove crufty "mem=" details
+ Michael Kerrisk
+ Remove crufty details on IBM MCA bus devices
+ Michael Kerrisk
+ Remove 'swap=" details
+ This seems to have gone away in Linux 2.2,
+ Michael Kerrisk
+ Remove crufty floppy disk driver options
+ In the specific case of floppy drives: the drivers still
+ exist, but it's been a while since most of saw these devices
+ in the wild. So, just refer the reader to the kernel source
+ file for details. (The detail in this man page was after all
+ originally drawn from that file.)
+ Remove crufty "ISDN drivers" options
+ Michael Kerrisk
+ Remove crufty "line printer driver" options
+ Michael Kerrisk
+ Remove crufty "Serial port drivers" options
+ Michael Kerrisk
+ Remove crufty reference to CONFIG_BUGi386
+ That option disappeared in Linux 2.4.
+ Michael Kerrisk
+ Remove crufty text
+ "bootsetups array" dates from Linux 2.0.
+ Michael Kerrisk
+ Remove crufty "Video hardware" options
+ Michael Kerrisk
+ Remove crufty SCSI device driver options
+
+fanotify.7
+ Michael Kerrisk [Heinrich Schuchardt]
+ Since Linux 3.19, fallocate(2) generates FAN_MODIFY events
+
+inotify.7
+ Michael Kerrisk [Heinrich Schuchardt]
+ Since Linux 3.19, fallocate(2) generates IN_MODIFY events
+
+ip.7
+ Michael Kerrisk
+ Explain how IP_ADD_MEMBERSHIP determines its argument type
+ Michael Kerrisk [Jiri Pirko, Magnus REFTEL]
+ Clarify details of the IP_MULTICAST_IF socket option
+ Michael Kerrisk [Advait Dixi]
+ Remove dubious text that says that SO_PRIORITY sets IP TOS
+ See https://bugzilla.kernel.org/show_bug.cgi?id=35852
+ Michael Kerrisk
+ Relocate misplaced text describing ENOPROTOOPT error
+
+packet.7
+ Graham Shaw
+ Add sll_protocol to list of required fields for outbound packets
+
+pthreads.7
+ Michael Kerrisk [KOSAKI Motohiro]
+ Using thread IDs whose lifetime has expired gives undefined behavior
+ See https://bugzilla.kernel.org/show_bug.cgi?id=53061
+
+raw.7
+ Michael Kerrisk [Tetsuo Handa]
+ For incoming datagrams, sin_port is set to zero
+ Michael Kerrisk
+ Mention sendto(), recvfrom(), and so on when discussing address format
+ This gives the reader a little context for the following
+ discussion of 'sin_port'.
+ Michael Kerrisk
+ Remove crufty reference to <netinet/in.h>
+ Michael Kerrisk
+ Replace reference to RFC 1700 with pointer to IANA protocol number list
+
+signal.7
+ Michael Kerrisk [Steinar H. Gunderson]
+ Clarify that I/O operations on disks are not interrupted by signals
+ See https://bugzilla.kernel.org/show_bug.cgi?id=97721
+
+unix.7
+ Michael Kerrisk [Christophe Lohr]
+ Remove mention of UNIX_PATH_MAX
+ This kernel constant is not exposed to user space.
+ Michael Kerrisk
+ Note the 108 bytes for sun_path is how things are done on Linux
+ And refer the reader to NOTES for discussion of portability.
+
+xattr.7
+ Michael Kerrisk
+ Document EA limits for Btrfs
+ Michael Kerrisk
+ Document VFS-imposed limits on EAs
+ VFS imposes a 255-byte limit on EA names, and a 64kB limit on
+ EA values.
+ Michael Kerrisk
+ The ext[234] block limitation applies to sum of all EAs
+ It is not a per-EA limit.
+ Michael Kerrisk
+ Clarify permissions required to work with 'user' EAs
+ Michael Kerrisk
+ ext2 and ext3 no longer need mounting with 'user_xattr' for user EAs
+ Michael Kerrisk
+ Add various relevant pages to SEE ALSO
+ Michael Kerrisk
+ Add CONFORMING TO section
+ Michael Kerrisk
+ Modify headings to man-pages norms
+ Michael Kerrisk
+ Btrfs also supports extended attributes
+ Michael Kerrisk
+ File capabilities are implemented using *security* attributes
+ Not *system* attributes
+ Michael Kerrisk
+ Describe limit on EA values for JFS, XFS, and Reiserfs
+ Michael Kerrisk
+ Explicitly mention some of the xattr system calls in DESCRIPTION
+ Naming the system calls helps to orient the reader
+
+nscd.8
+ Michael Kerrisk
+ Add mention of 'services' and 'netgroup' databases
+ This makes the page consistent with nscd.conf(5).
+
+
+==================== Changes in man-pages-4.01 ====================
+
+Released: 2015-07-23, Munich
+
+
+Contributors
+------------
+
+The following people contributed patches/fixes or (noted in brackets
+in the changelog below) reports, notes, and ideas that have been
+incorporated in changes in this release:
+
+Alexei Starovoitov <ast@plumgrid.com>
+Andries E. Brouwer <Andries.Brouwer@cwi.nl>
+Arjun Shankar <arjun@redhat.com>
+Ashish Sangwan <a.sangwan@samsung.com>
+Ben Woodard <woodard@redhat.com>
+Carlos O'Donell <carlos@redhat.com>
+Christoph Thompson <cjsthompson@gmail.com>
+Cortland Setlow <cortland.setlow@gmail.com>
+Daniel Borkmann <daniel@iogearbox.net>
+David Leppik <dleppik@vocalabs.com>
+Dilyan Palauzov <dilyan.palauzov@aegee.org>
+Doug Klima <cardoe@gentoo.org>
+Eric B Munson <emunson@akamai.com>
+Florian Weimer <fweimer@redhat.com>
+Hack NDo <hackndo@gmail.com>
+Jann Horn <jann@thejh.net>
+Jens Axboe <axboe@fb.com>
+Jian Wen <wenjianhn@gmail.com>
+Joerg Roedel <jroedel@suse.de>
+Julian Orth <ju.orth@gmail.com>
+Kees Cook <keescook@chromium.org>
+Laszlo Ersek <lacos@caesar.elte.hu>
+Marko Myllynen <myllynen@redhat.com>
+Mehdi Aqadjani Memar <m.aqadjanimemar@student.vu.nl>
+Michael Kerrisk <mtk.manpages@gmail.com>
+Michal Hocko <mhocko@suse.cz>
+Mike Frysinger <vapier@gentoo.org>
+Mike Hayward <hayward@loup.net>
+Miklos Szeredi <miklos@szeredi.hu>
+Namhyung Kim <namhyung@gmail.com>
+Namjae Jeon <namjae.jeon@samsung.com>
+Nathan Lynch <nathan_lynch@mentor.com>
+NeilBrown <neilb@suse.de>
+Pádraig Brady <P@draigBrady.com>
+Pavel Machek <pavel@ucw.cz>
+Peter Hurley <peter@hurleysoftware.com>
+Sam Varshavchik <mrsam@courier-mta.com>
+Scot Doyle <lkml14@scotdoyle.com>
+Stephan Mueller <stephan.mueller@atsec.com>
+Tobias Stoeckmann <tobias@stoeckmann.org>
+Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
+Uwe Kleine-König <uwe+debian@kleine-koenig.org>
+Vegard Nossum <vegard.nossum@oracle.com>
+Ville Skyttä <ville.skytta@iki.fi>
+Vince Weaver <vincent.weaver@maine.edu>
+Zeng Linggang <zenglg.jy@cn.fujitsu.com>
+文剑 <wenjianhn@gmail.com>
+
+Apologies if I missed anyone!
+
+
+New and rewritten pages
+-----------------------
+
+bpf.2
+ Alexei Starovoitov, Michael Kerrisk [Daniel Borkmann]
+ New page documenting bpf(2)
+
+__ppc_get_timebase.3
+ Tulio Magno Quites Machado Filho
+ New page documenting __ppc_get_timebase() and __ppc_get_timebase_freq()
+ Glibc 2.16 was released with a new function for the Power
+ architecture that can read its Time Base Register.
+ Glibc 2.17 adds a function to read the frequency at which the Time
+ Base Register of Power processors is updated.
+
+queue.3
+ Michael Kerrisk [David Leppik, Doug Klima]
+ Reimport from latest FreeBSD page
+ Long ago, Doug Klima noted that many macros were not
+ documented in the queue(3) page. Fix by reimporting from
+ latest [1] FreeBSD man page.
+
+ [1] Revision 263142, Modified Fri Mar 14 03:07:51 2014 UTC
+
+ This also fixes https://sourceware.org/bugzilla/show_bug.cgi?id=1506
+
+ This time, I'll learn from past mistakes and not convert
+ from 'mdoc' to 'man' macros.
+ Michael Kerrisk
+ Use subsections in DESCRIPTION
+ Michael Kerrisk
+ Remove SEE ALSO reference to nonexistent tree(3)
+ Michael Kerrisk
+ Use real hyphens in code samples
+ Michael Kerrisk
+ Comment out text for functions not in glibc
+ Michael Kerrisk
+ Replace HISTORY with CONFORMING TO
+
+
+Newly documented interfaces in existing pages
+---------------------------------------------
+
+rename.2
+ Michael Kerrisk [Miklos Szeredi]
+ Document RENAME_WHITEOUT
+ Heavily based on text by Miklos Szeredi.
+
+
+New and changed links
+---------------------
+
+__ppc_get_timebase_freq.3
+ Tulio Magno Quites Machado Filho
+ New link to new __ppc_get_timebase(3) page
+
+LIST_EMPTY.3
+LIST_FIRST.3
+LIST_FOREACH.3
+LIST_HEAD_INITIALIZER.3
+LIST_INSERT_BEFORE.3
+LIST_NEXT.3
+SLIST_EMPTY.3
+SLIST_ENTRY.3
+SLIST_FIRST.3
+SLIST_FOREACH.3
+SLIST_HEAD.3
+SLIST_HEAD_INITIALIZER.3
+SLIST_INIT.3
+SLIST_INSERT_AFTER.3
+SLIST_INSERT_HEAD.3
+SLIST_NEXT.3
+SLIST_REMOVE.3
+SLIST_REMOVE_HEAD.3
+STAILQ_CONCAT.3
+STAILQ_EMPTY.3
+STAILQ_ENTRY.3
+STAILQ_FIRST.3
+STAILQ_FOREACH.3
+STAILQ_HEAD.3
+STAILQ_HEAD_INITIALIZER.3
+STAILQ_INIT.3
+STAILQ_INSERT_AFTER.3
+STAILQ_INSERT_HEAD.3
+STAILQ_INSERT_TAIL.3
+STAILQ_NEXT.3
+STAILQ_REMOVE.3
+STAILQ_REMOVE_HEAD.3
+TAILQ_CONCAT.3
+TAILQ_EMPTY.3
+TAILQ_FIRST.3
+TAILQ_FOREACH.3
+TAILQ_FOREACH_REVERSE.3
+TAILQ_HEAD_INITIALIZER.3
+TAILQ_INSERT_BEFORE.3
+TAILQ_LAST.3
+TAILQ_NEXT.3
+TAILQ_PREV.3
+TAILQ_SWAP.3
+ Michael Kerrisk
+ New links to queue.3
+
+
+Global changes
+--------------
+
+Various pages
+ Michael Kerrisk [Andries E. Brouwer]
+ Remove "ABI" from "C library/kernel ABI differences" subheadings
+ The "ABI" doesn't really convey anything significant in
+ the title. These subsections are about describing differences
+ between the kernel and (g)libc interfaces.
+
+
+Changes to individual pages
+---------------------------
+
+intro.1
+ Michael Kerrisk [Andries E. Brouwer]
+ Drop intro paragraph on '$?' shell variable
+ As Andries notes, this piece of text is rather out of place in
+ a page that was intended to provide a tutorial introduction for
+ beginners logging in on a Linux system.
+
+locale.1
+ Marko Myllynen
+ A minor output format clarification
+ A minor clarification for the locale output format which was
+ brought up at
+ https://sourceware.org/bugzilla/show_bug.cgi?id=18516.
+
+ For reference, see
+ https://sourceware.org/bugzilla/show_bug.cgi?id=18516
+ http://pubs.opengroup.org/onlinepubs/9699919799/utilities/locale.html
+
+ Add CONFORMING TO section
+
+capget.2
+ Julian Orth
+ Clarify that hdrp->pid==0 is equivalent gettid() not getpid()
+
+chroot.2
+ Jann Horn
+ chroot() is not intended for security; document attack
+ It is unfortunate that this discourages this use of chroot(2)
+ without pointing out alternative solutions - for example,
+ OpenSSH and vsftpd both still rely on chroot(2) for security.
+
+ Bind mounts should theoretically be usable as a replacement, but
+ currently, they have a similar problem (CVE-2015-2925) that hasn't
+ been fixed in ~6 months, so I'd rather not add it to the manpage
+ as a solution before a fix lands.
+
+clock_getres.2
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+eventfd.2
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+execve.2
+ Michael Kerrisk
+ Elaborate on envp/argv as NULL behavior
+
+_exit.2
+ Michael Kerrisk
+ Open stdio frames are not flushed, temporary files are deleted
+ Many years ago, text was added to the page saying that it is
+ implementation-dependent whether stdio streams are flushed and
+ whether temporary are removed. In part, this change appears to
+ be because POSIX.1-2001 added text related to this point.
+ However, that seems to have been an error in POSIX, and the
+ text was subsequently removed for POSIX.1-2008. See
+ https://collaboration.opengroup.org/austin/interps/documents/9984/AI-085.txt
+ Austin Group Interpretation reference 1003.1-2001 #085
+
+fallocate.2
+ Namjae Jeon [Michael Kerrisk]
+ Document FALLOC_FL_INSERT_RANGE
+ Michael Kerrisk
+ Since Linux 4.2, ext4 supports FALLOC_FL_INSERT_RANGE
+
+fcntl.2
+ Michael Kerrisk
+ OFD locks are proposed for inclusion in the next POSIX revision
+
+getrlimit.2
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getrusage.2
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+gettid.2
+ Michael Kerrisk
+ Note that for a thread group leader, gettid() == getpid()
+
+iopl.2
+ Michael Kerrisk
+ Remove some historical libc5 and glibc 1 details
+ These details are ancient, and long ago ceased to be relevant.
+
+ioprio_set.2
+ Michael Kerrisk [Jens Axboe]
+ Document meaning of ioprio==0
+
+mlock.2
+ Michael Kerrisk [Mehdi Aqadjani Memar]
+ Document another ENOMEM error case
+ ENOMEM can occur if locking/unlocking in the middle of a region
+ would increase the number of VMAs beyond the system limit (64k).
+
+mmap.2
+ Michal Hocko [Eric B Munson]
+ Clarify MAP_POPULATE
+ David Rientjes has noticed that MAP_POPULATE wording might promise
+ much more than the kernel actually provides and intends to provide.
+ The primary usage of the flag is to pre-fault the range. There is
+ no guarantee that no major faults will happen later on. The pages
+ might have been reclaimed by the time the process tries to access
+ them.
+ Michal Hocko [Eric B Munson]
+ Clarify MAP_LOCKED semantics
+ MAP_LOCKED had a subtly different semantic from mmap(2)+mlock(2)
+ since it has been introduced.
+ mlock(2) fails if the memory range cannot get populated to
+ guarantee that no future major faults will happen on the range.
+ mmap(MAP_LOCKED) on the other hand silently succeeds even if
+ the range was populated only partially.
+
+ Fixing this subtle difference in the kernel is rather awkward
+ because the memory population happens after mm locks have been
+ dropped and so the cleanup before returning failure (munlock)
+ could operate on something else than the originally mapped area.
+
+ E.g. speculative userspace page fault handler catching SEGV and
+ doing mmap(fault_addr, MAP_FIXED|MAP_LOCKED) might discard portion
+ of a racing mmap and lead to lost data. Although it is not clear
+ whether such a usage would be valid, mmap page doesn't explicitly
+ describe requirements for threaded applications so we cannot
+ exclude this possibility.
+
+ This patch makes the semantic of MAP_LOCKED explicit and suggests
+ using mmap + mlock as the only way to guarantee no later major
+ page faults.
+ Michael Kerrisk
+ ERRORS: point out that ENOMEM can occur even for munmap()
+
+mprotect.2
+ Michael Kerrisk
+ Note ENOMEM error that can occur when we reach limit on maximum VMAs
+
+open.2
+read.2
+write.2
+ Michael Kerrisk [Mike Hayward]
+ Clarify that O_NONBLOCK is a no-op for regular files and block devices
+
+perf_event_open.2
+ Vince Weaver [Joerg Roedel]
+ Exclude_host/exclude_guest clarification
+ This patch relates to the exclude_host and exclude_guest bits added
+ by the following commit:
+
+ exclude_host, exclude_guest; Linux 3.2
+ commit a240f76165e6255384d4bdb8139895fac7988799
+ Author: Joerg Roedel <joerg.roedel@amd.com>
+ Date: Wed Oct 5 14:01:16 2011 +0200
+
+ perf, core: Introduce attrs to count in either host or guest mode
+
+ The updated manpage text clarifies that the "exclude_host" and
+ "exclude_guest" perf_event_open() attr bits only apply in the
+ context of a KVM environment and are currently x86 only.
+ Vince Weaver
+ Document PERF_SAMPLE_REGS_INTR
+ This patch relates to the addition of PERF_SAMPLE_REGS_INTR
+ support added in the following commit:
+
+ perf_sample_regs_intr; Linux 3.19
+ commit 60e2364e60e86e81bc6377f49779779e6120977f
+ Author: Stephane Eranian <eranian@google.com>
+
+ perf: Add ability to sample machine state on interrupt
+
+ The primary difference between PERF_SAMPLE_REGS_INTR and the
+ existing PERF_SAMPLE_REGS_USER is that the new support will
+ return kernel register values. Also if precise_ip is
+ set higher than 0 then the PEBS register state will be returned
+ rather than the saved interrupt state.
+
+ This patch incorporates feedback from Stephane Eranian and
+ Andi Kleen.
+
+prctl.2
+seccomp.2
+ Michael Kerrisk
+ Clarify that SECCOMP_SET_MODE_STRICT disallows exit_group(2)
+ These days, glibc implements _exit() as a wrapper around
+ exit_group(2). (When seccomp was originally introduced, this was
+ not the case.) Give the reader a clue that, despite what glibc is
+ doing, what SECCOMP_SET_MODE_STRICT permits is the true _exit(2)
+ system call, and not exit_group(2).
+
+pread.2
+read.2
+readv.2
+sendfile.2
+write.2
+ Michael Kerrisk
+ Clarify that Linux limits transfers to a maximum of 0x7ffff000 bytes
+ See https://bugs.debian.org/629994 and
+ https://bugs.debian.org/630029.
+
+pread.2
+ Michael Kerrisk
+ Rewrite RETURN VALUE section
+ (Also drop the text on pwrite() returning zero; that seems bogus.)
+
+ptrace.2
+ Michael Kerrisk [Vegard Nossum]
+ PTRACE_O_TRACEEXIT clarification
+
+readv.2
+ Michael Kerrisk
+ Remove BUGS heading
+ The text on mixing I/O syscalls and stdio is a general point
+ of behavior. It's not a bug as such.
+
+recv.2
+send.2
+ Michael Kerrisk
+ Explain some subtleties of MSG_DONTWAIT versus O_NONBLOCK
+
+rename.2
+ Michael Kerrisk
+ Michael Kerrisk
+ Note that RENAME_NOREPLACE can't be employed with RENAME_EXCHANGE
+
+sched_setaffinity.2
+ Michael Kerrisk
+ Add an example program
+ Michael Kerrisk [Florian Weimer]
+ Explain how to deal with 1024-CPU limitation of glibc's cpu_set_t type
+ Michael Kerrisk
+ Mention the use of the 'isolcpus' kernel boot option
+
+sched_setattr.2
+ Julian Orth
+ Remove a const attribute
+ The attr argument of sched_setattr was documented as const but the
+ kernel will modify the size field of this struct if it contains an
+ invalid value. See the documentation of the size field for details.
+
+seccomp.2
+ Michael Kerrisk
+ SEE ALSO: add bpf(2)
+
+send.2
+ Michael Kerrisk
+ Expand on subtleties of MSG_NOSIGNAL versus ignoring SIGPIPE
+
+sigaltstack.2
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+socket.2
+ Stephan Mueller
+ Update documentation reference for AF_ALG
+
+truncate.2
+ Michael Kerrisk
+ ERRORS: ftruncate() can fail if the file descriptor is not writable
+
+utimensat.2
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+ After research, We think utimensat() and futimens() are thread-safe.
+ But, there are not markings of utimensat() and futimens() in glibc
+ document.
+
+clearenv.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is not thread-safe
+
+dl_iterate_phdr.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+error.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+fexecve.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+fpurge.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+fread.3
+ Andries E. Brouwer
+ Clarify terminology
+ In the "RETURN VALUE" section the word item is in italics
+ as if it were one of the function parameters. But the word
+ "item" occurs here for the first time, earlier the text
+ uses "element". [Patch improves this.]
+
+fts.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+getaddrinfo.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getaddrinfo_a.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getauxval.3
+ Michael Kerrisk
+ File capabilities also trigger AT_SECURE
+ Michael Kerrisk
+ (Briefly) document AT_HWCAP2
+
+getgrent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+gethostbyname.3
+ Michael Kerrisk [Laszlo Ersek]
+ Remove mention of IPv6 addresses, which are not supported
+ As reported by Laszlo Ersek:
+
+ gethostbyname(3) fails to resolve the IPv6 address "::1",
+ but the manual page says: "If name is an IPv4 or IPv6 address,
+ no lookup is performed and gethostbyname() simply copies name
+ into the h_name field [...]".
+
+ Debian bug report:
+ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455762
+
+ glibc bug report:
+ http://sourceware.org/bugzilla/show_bug.cgi?id=5479
+
+ SUSv3 link for gethostbyname(3):
+ http://www.opengroup.org/onlinepubs/000095399/functions/gethostbyname.html
+
+ It seems that the glibc behavior is conformant, and the manual
+ page is in error.
+
+getifaddrs.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getnameinfo.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+getnetent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getprotoent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+getprotoent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getpw.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+getpwent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+getrpcent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+getrpcent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+getrpcport.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+getservent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that aren't thread-safe
+
+getservent_r.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+gsignal.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+key_setsecret.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+malloc_get_state.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+malloc_info.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+malloc_stats.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+malloc_trim.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+MB_LEN_MAX.3
+ Michael Kerrisk
+ Clarify meaning of MB_LEN_MAX
+ Michael Kerrisk [Pádraig Brady]
+ MB_LEN_MAX is 16 in modern glibc versions
+
+memcpy.3
+ Michael Kerrisk
+ NOTES: describe the glibc 2.13 changes that revealed buggy applications
+ Adding a note on this point seems worthwhile as a way of
+ emphasizing the point that the buffers must not overlap.
+
+mq_notify.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+perror.3
+ Michael Kerrisk
+ Some wording improvements and clarifications
+
+profil.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is not thread-safe
+
+psignal.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+pthread_attr_init.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+ Michael Kerrisk
+ Use "%zd" for printing size_t in example code
+
+pthread_attr_setaffinity_np.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+pthread_cancel.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+pthread_cleanup_push.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+pthread_create.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+pthread_detach.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+pthread_getattr_np.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+pthread_join.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+pthread_setname_np.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+pthread_tryjoin_np.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+putgrent.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+rcmd.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+resolver.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+rpc.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+rpmatch.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+sem_close.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+sem_open.3
+ Zeng Linggang
+ ATTRIBUTES: Note function that is thread-safe
+
+setaliasent.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are/aren't thread-safe
+
+setlocale.3
+ Marko Myllynen
+ Update CONFORMING TO
+ http://pubs.opengroup.org/onlinepubs/9699919799/functions/setlocale.html
+
+setlocale.3
+ Marko Myllynen
+ Tweak C/POSIX locale portability description
+ As discussed earlier, the current description might be a little
+ bit too stringent, let's avoid the issue by describing the
+ portability aspect on a slightly higher level.
+
+ References:
+
+ http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap06.html
+ http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap07.html
+ http://pubs.opengroup.org/onlinepubs/9699919799/functions/setlocale.html
+
+shm_open.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+strfmon.3
+ Marko Myllynen
+ Document strfmon_l(3)
+ Describe strfmon_l(3).
+
+ http://pubs.opengroup.org/onlinepubs/9699919799/functions/strfmon.html
+ Marko Myllynen
+ Fix CONFORMING TO
+ AFAICS strfmon(3) is now defined in POSIX and the glibc
+ implementation is as specified there.
+
+ http://pubs.opengroup.org/onlinepubs/9699919799/functions/strfmon.html
+ Marko Myllynen
+ Rewrite the example
+ I think the example is more accurate when we use the exact
+ locale names and also the Euro sign where appropriate.
+
+xcrypt.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+xdr.3
+ Zeng Linggang
+ ATTRIBUTES: Note functions that are thread-safe
+
+console_codes.4
+ Scot Doyle [Pavel Machek, Michael Kerrisk]
+ Add CSI sequence for cursor blink interval
+ Add a Console Private CSI sequence to specify the current
+ console's cursor blink interval. The interval is specified
+ as a number of milliseconds until the next cursor display
+ state toggle, from 50 to 65535.
+
+null.4
+ Michael Kerrisk
+ Note that reads from /dev/zero are interruptible since Linux 2.6.31
+
+core.5
+ Michael Kerrisk
+ Mention 'coredump_filter' boot option
+
+host.conf.5
+ Michael Kerrisk
+ Wording fix: s/resolv+/the resolver library/
+ The term "resolv+" seems to be historical cruft.
+
+hosts.equiv.5
+ Carlos O'Donell
+ Fix format, clarify IdM needs, and provide examples.
+ In some recent work with a Red Hat customer I had the opportunity
+ to discuss the fine nuances of the ruserok() function and related
+ API which are used to implement rlogin and rsh.
+
+ It came to my attention after working with QE on some automated
+ internal testing that there were no good examples in the hosts.equiv
+ manual page showing how the format was supposed to work for this
+ file and for ~/.rhosts, worse the "format" line showed that there
+ should be spaces between arguments when that would clearly lead
+ to incorrect behaviour. In addition some things that the format
+ allows you to write are just wrong like "-host -user" which makes
+ no sense since the host is already rejected, and should be written
+ as "host -user" instead. I added notes in the example to make it
+ clear that "-host -user" is invalid.
+
+ I fixed three things:
+
+ (a) The format line.
+ - Either +, or [-]hostname, or +@netgrp or -@netgrp.
+ - Either +, or [-]username, or +@netgrp or -@netgrp.
+ - You must specify something in the hostname portion so remove
+ optional brackets.
+
+ (b) Clarify language around credentials
+ - If the host is not trusted you must provide credentials to
+ the login system and that could be anything really and it
+ depends on your configuration e.g. PAM or whatever IdM you have.
+
+ (c) Provide real-world examples
+ - Provide several real world examples and some corner case
+ examples for how you would write something. Hopefully others
+ can add examples as they see fit.
+ Michael Kerrisk [Carlos O'Donell, Arjun Shankar]
+ Improve explanation in EXAMPLE
+
+locale.5
+ Marko Myllynen
+ Document map to_inpunct, map to_outpunct
+ See e.g. fa_IR for reference.
+ Marko Myllynen
+ Document class in LC_CTYPE
+ See e.g. the locale zh_CN and
+
+ http://en.cppreference.com/w/cpp/string/wide/towctrans
+ http://en.cppreference.com/w/cpp/string/wide/wctrans
+ Marko Myllynen
+ Add iconv(1) reference
+ Marko Myllynen
+ Document character transliteration
+ See e.g. da_DK for reference.
+
+ (Not sure should we actually provide an example here?)
+ Marko Myllynen
+ Document era keywords
+ This patch completes the LC_TIME section - since these era
+ keywords are so tightly coupled, I'm providing them as a
+ single patch.
+
+ Based on
+ http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html
+ http://www.open-std.org/jtc1/SC22/WG20/docs/n972-14652ft.pdf
+ Marko Myllynen
+ Document default_missing
+ Marko Myllynen
+ Document outdigit and alt_digits
+ See e.g. fa_IR for reference.
+ Marko Myllynen
+ Refer to locale(7) more prominently
+ It's probably a good idea to refer to locale(7) so that a reader
+ can check what a category is about before describing them in
+ detail.
+ Marko Myllynen
+ Document charclass and charconv
+ See e.g. the locales ja_JP and ko_KR and
+
+ http://en.cppreference.com/w/cpp/string/wide/towctrans
+ http://en.cppreference.com/w/cpp/string/wide/wctrans
+ Marko Myllynen
+ Copy is not exclusive in LC_CTYPE and LC_COLLATE
+ See e.g. da_DK for reference.
+ Marko Myllynen
+ Remove the FIXME for timezone
+ The timezone of LC_TIME is not in POSIX, only 6 (out of ~300)
+ glibc locales define it, the glibc code comment below from
+ glibc.git/programs/ld-time.c seems to suggest it's not a good
+ idea, and there's been a proposal in upstream [1] to remove the
+ existing timezone definitions from glibc locales so I think
+ it's actually better to leave this one undocumented:
+
+ /* XXX We don't perform any tests on the timezone value since this is
+ simply useless, stupid $&$!@... */
+
+ 1) https://sourceware.org/ml/libc-alpha/2015-06/msg00098.html
+
+ Move the remaining LC_COLLATE FIXMEs together while at it.
+ Marko Myllynen
+ Fix country_isbn format
+ Both plain numbers and Unicode code points are used in
+ glibc locales but checking the code reveals that country_isbn
+ is handled like the rest of its category expect for country_num
+ which was clarified earlier.
+ Marko Myllynen
+ Sort according to the standard
+ Sort the options so that those defined in POSIX are listed first,
+ then followed by those defined in ISO/IEC TR 14652 in the order
+ of common convention in many widely used glibc locales.
+
+ Actual descriptions are unchanged.
+
+ http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap07.html
+ Marko Myllynen
+ Refer to strftime(3) where appropriate
+ The relationship between the locale time format syntax
+ and strftime() cannot be considered as obvious.
+ Marko Myllynen
+ Document map "totitle"
+ See e.g. locales/i18n for reference.
+ Michael Kerrisk [Marko Myllynen]
+ Remove BUGS section saying man page is not complete
+ To some degree, this is true of many pages. And anyway, this
+ page is much better after recent work by Marko.
+
+proc.5
+ Michael Kerrisk
+ List /proc/vmstat fields
+ Michael Kerrisk
+ Tweak /proc/vmstat text
+ Michael Kerrisk
+ Add /proc/crypto entry with a pointer to further information
+ Michael Kerrisk [Kees Cook]
+ Document /proc/sys/kernel/sysctl_writes_strict
+ Based on text in Documentation/sysctl/kernel.txt.
+ Michael Kerrisk
+ Move misordered /proc/[pid]/timers entry
+ Michael Kerrisk
+ Refer to bpf(2) for explanation of /proc/sys/net/core/bpf_jit_enable
+
+repertoiremap.5
+ Marko Myllynen
+ Symbolic names AKA mnemonics
+ A long time ago in glibc, repertoire maps were used (but they
+ were removed already in 2000), those mapping files were named
+ as mnemonics, so "mnemonic" is a term that would almost
+ certainly come up if somebody studies glibc side (perhaps even
+ the related standards like ISO 9945 [which I don't have access
+ to]) so I thought it's worth to mention to term in the man page
+ to make sure we're talking about the same thing, otherwise
+ someone might wonder is that something different or not.
+
+ IOW, symbolic names and mnemonics are often used interchangeably,
+ let's mention the other often used term in the page, too.
+
+capabilities.7
+ Michael Kerrisk
+ CAP_SYS_ADMIN allows calling bpf(2)
+
+locale.7
+ Marko Myllynen
+ LC_CTYPE determines transliteration rules on glibc systems
+
+packet.7
+ 文剑 [Cortland Setlow]
+ Fix description of binding a packet socket to an interface
+
+pty.7
+ NeilBrown [Peter Hurley]
+ Clarify asynchronous nature of PTY I/O
+ A PTY is not like a pipe - there may be delayed between data
+ being written at one end and it being available at the other.
+
+ This became particularly apparent after
+ commit f95499c3030f
+ ("n_tty: Don't wait for buffer work in read() loop")
+ in Linux 3.12
+
+ See also the mail thread at https://lkml.org/lkml/2015/5/1/35
+ Date Mon, 04 May 2015 12:32:04 -0400
+ From Peter Hurley <>
+ Subject Re: [PATCH bisected regression] input_available_p()
+ sometimes says 'no' when it should say 'yes'
+
+rtld-audit.7
+ Ben Woodard
+ Use correct printf() specifier for pointer types
+ In the example code you used %x rather than %p in the example
+ code for an audit library. The problem is that it truncates the
+ pointers on 64b platforms. So you get something like:
+
+ la_symbind64(): symname = strrchr sym->st_value = 0x7f4b8a3f8960
+ ndx = 222 flags = 0x0 refcook = 8b53e5c8 defcook = 8b537e30
+
+ rather than:
+
+ la_symbind64(): symname = fclose sym->st_value = 0x7fa452dd49b0
+ ndx = 1135 flags = 0x0 refcook = 0x7fa453f395c8 defcook = 0x7fa453f32e30
+
+ This has bitten me a handful of times when playing around with
+ audit test libraries to investigate its behavior.
+
+sched.7
+ Michael Kerrisk
+ Remove ancient, wildly optimistic prediction about future of RT patches
+ It seems the patches were not merged by 2.6.30...
+
+socket.7
+ Michael Kerrisk
+ SEE ALSO: add bpf(2)
+
+vdso.7
+ Nathan Lynch [Mike Frysinger]
+ Update for ARM
+ The 32-bit ARM architecture in Linux has gained a vDSO as of the
+ 4.1 release. (I was the primary author.)
+
+ Document the symbols exported by the ARM VDSO.
+
+ Accepted kernel submission:
+ http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/332573.html
projects / thirdparty / man-pages.git / blobdiff