LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity
16,943 Commits 1 Branch 197 Tags 93 MiB
Commit Graph

16943 Commits

Author SHA1 Message Date
Michael Kerrisk 218081bfff fuse.4: wfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 15:20:57 +01:00
Michael Kerrisk 17f022f2a6 send.2: tfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 15:18:59 +01:00
Michael Kerrisk dc5186fe54 getrlimit.2: tfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 15:18:35 +01:00
Michael Kerrisk 6e01a8b826 intro.5: Document the reality that by now Section 5 also covers filesystems 
There are by now, from various filesystem projects, various
pages in Section 5 that document differnt filesystems.
Change intro(5) to reflect that.

Documented after following: http://bugs.debian.org/847998

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 14:53:27 +01:00
Michael Kerrisk 4a8449e127 mlock.2: Note pre-4.9 bug in RLIMIT_MEMLOCK accounting for overlapping locks 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 13:34:47 +01:00
Michael Kerrisk 7509f758ce capabilities.7: Document a new use of CAP_SYS_RESOURCE 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 12:29:08 +01:00
Michael Kerrisk ee3d7b3b46 getrlimit.2: Various minor wording fixes 
Mainly: use complete sentence to introduce each limit.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 12:18:57 +01:00
Michael Kerrisk 9ca2e0c114 unix.7: tfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 11:30:16 +01:00
Michael Kerrisk ece9c9e301 recv.2: SEE ALSO: add ip(7), ipv6(7), tcp(7), udp(7), unix(7) 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 10:55:03 +01:00
Michael Kerrisk b9cde4611c send.2: SEE ALSO: add ipv6(7), socket(7), unix(7) 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 10:54:32 +01:00
Michael Kerrisk dd55b8a1d7 capabilities.7: tfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 09:19:01 +01:00
Michael Kerrisk 24ee13dfc1 capabilities.7: Add another case for CAP_DAC_READ_SEARCH 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 09:10:40 +01:00
Michael Kerrisk 217d573862 link.2: When using linkat() AT_EMPTY_PATH, 'olddirfd' must not be a directory 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-16 09:09:33 +01:00
Michael Kerrisk 968b27aa1a capabilities.7: Add some more operations governed by CAP_SYS_ADMIN 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 20:53:50 +01:00
Michael Kerrisk c6ddae522e capabilities.7: Add a few more operations covered by CAP_SYS_ADMIN 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 19:18:11 +01:00
Michael Kerrisk e1d2d7740e scandir.3: Minor reworking of text for example program 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 14:30:43 +01:00
Michael Kerrisk 9a96fb657c scandir.3: Improve logic of the example program 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 14:30:43 +01:00
Michael Kerrisk 5e84ae6cd6 scandir.3: Fix errors in example program 
See http://bugs.debian.org/848231.

Reported-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 14:30:43 +01:00
Michael Kerrisk eb359b3e8f prctl.2: wfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 12:47:59 +01:00
Michael Kerrisk 224d55c497 prctl.2: wfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 12:47:59 +01:00
Michael Kerrisk 1a52f4f6e2 prctl.2: Clarify that the ambient capability set is per-thread 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 12:47:59 +01:00
Michael Kerrisk 3b21b29e5c execve.2: File capabilities can be ignored for the same reasons as set-UID/set-GID 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 12:47:59 +01:00
Michael Kerrisk 9faff76894 execve.2: wfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 12:47:59 +01:00
Michael Kerrisk 56cc88cbdc capabilities.7: Refer to execve(2) for the reasons that file capabilities may be ignored 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 12:47:59 +01:00
Michael Kerrisk f04f131fa9 capabilities.7: ffix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 12:47:59 +01:00
Michael Kerrisk fca269a950 execve.2: The 'no_new_privs' bit inhibits transformations of the effective IDs 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 12:47:59 +01:00
Michael Kerrisk 29294c4237 execve.2: Rework text describing when effective IDs aren't transformed by execve() 
Mainly in preparation for addition of information about
no_new_privs bit.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 12:47:39 +01:00
Michael Kerrisk 40dfb5bafb prctl.2: The no_new_privs setting is per-thread (not per-process) 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 09:08:10 +01:00
Michael Kerrisk 4d850396e8 prctl.2: Add reference to seccomp(2) on discussion of PR_SET_NO_NEW_PRIVS 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 09:07:17 +01:00
Michael Kerrisk c70fea6e4f prctl.2: Mention /proc/PID/status 'NoNewPrivs' field 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 09:07:17 +01:00
Michael Kerrisk 6c0ed8735b proc.5: Document /proc/PID/status 'NoNewPrivs' filed 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-15 08:38:55 +01:00
Michael Kerrisk fa72c2244f namespaces.7: tfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-14 11:52:55 +01:00
Michael Kerrisk 091771e94b filesystems.5: SEE ALSO: add btrfs(5), nfs(5), tmpfs(5) 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-13 12:11:36 +01:00
Michael Kerrisk 05babf32a0 random.4: Note that entropY-avail will be a number in the range 0..4096 
Reported-by: Jon Jensen <jon@endpoint.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-13 12:11:36 +01:00
Michael Kerrisk 7c28a0b660 random.7: SEE ALSO: add getauxval(3) 
A small hint to the reader that some random bytes arrive
in the auxiliary vector.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-13 12:11:32 +01:00
Michael Kerrisk 330e88474e sleep.3: Note that sleep() is implemented via nanosleep(2) 
See https://bugzilla.kernel.org/show_bug.cgi?id=73371.

Reported-by: Mike Frysiner <vapier@gentoo.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-13 09:31:21 +01:00
Michael Kerrisk 0d28787bbd sleep.3: Convert BUGS text to "Portability notes" subsection 
The existing text is not a bug, as such.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-13 09:27:39 +01:00
Michael Kerrisk 5272b4c4a4 sleep.3: Note that sleep() sleeps for a real-time number of seconds 
See https://bugzilla.kernel.org/show_bug.cgi?id=73371.

Reported-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-13 09:22:05 +01:00
Michael Kerrisk 5288e1f5ee sleep.3: DESCRIPTION: minor reworking 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-13 09:18:08 +01:00
Michael Kerrisk 1f6cc4a614 sleep.3: wfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-13 09:13:10 +01:00
Michael Kerrisk f086b6aad1 clock_getres.2: Note POSIX.1 requirements re relative time services and CLOCK_REALTIME 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-13 09:09:44 +01:00
Michael Kerrisk ff1203e5c2 exec.3: execl() and execle() were not async-signal-safe before glibc 2.24 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-12 12:53:05 +01:00
Michael Kerrisk aa30b3276d aio_suspend.3: Note that the glibc implementation is not async-signal-safe 
See https://sourceware.org/bugzilla/show_bug.cgi?id=13172

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-12 12:53:05 +01:00
Michael Kerrisk 46fc35d52b sem_post.3, setjmp.3: SEE ALSO: add signal-safety(7) 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-12 12:53:05 +01:00
Michael Kerrisk d077802826 fork.2, sigaction.2, signal.2: Amend cross references to point to signal-safety(7) 
The discussion of async-signal-safe functions has moved
to a new page.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-12 12:53:05 +01:00
Michael Kerrisk 67557cd9d1 signal-safety.7: Note async-signal-safety problems caused by pthread_atfork() 
See https://bugzilla.kernel.org/show_bug.cgi?id=25292

And there will likely be future changes as well.
Quoting http://www.opengroup.org/austin/aardvark/latest/xshbug3.txt:

    COMMENT                          Enhancement Request Number 15
    rajani.g.k:xxxxxx               Defect in XSH 2.4.3 (rdvk#  6)
    {GKRFORK012009}                   Thu, 8 Jan 2009 07:41:10 GMT

    [...]

    As per this section, XSH P1529, L49389-49402, it is possible
    that multithreaded libraries could be used by single threaded
    applications. In which case, atfork handlers are essential for
    the libraries to protect their internal state during fork. As
    explained further P1530, L49403-49404, pthread_atfork
    functions are mainly required to acquire/release mutex locks,
    for protecting the applications/libraries from fork() calls.
    C-library needs to as well have an atfork handler which
    acquires all the required locks to protect its memory state
    across fork().

    The acquire/release mutex calls themselves are aync-signal
    unsafe operations. Use of them makes pthread_atfork handlers
    async-signal unsafe which in turn makes fork() async-signal
    unsafe when called by an application which is multi threaded,
    or which is linked to a library which is multi threaded.

    Action:

    Need clarification with respect to
    1. Is it correct to list fork as an async-signal safe
    interface, in a multi threaded scenario?

    2. Can the implementation be allowed to not call the atfor
    handlers, when fork is called from a signal handler? If the
    atfork handlers are not going to be called when fork is called
    in the signal handler, then they can not be called, even if
    fork is called in the newly created child before exec.

    3. If only async-signal safe functions are to be called from
    pthread_atfork handlers, then how will multi-threaded librarie
    protect themselves by the fork calls, made by single threaded
    applications linked to them?

Reported-by: KASAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-12 12:53:05 +01:00
Michael Kerrisk fb16ec3585 signal-safety.7: Note glibc deviations from POSIX requirements 
See https://bugzilla.kernel.org/show_bug.cgi?id=25292

Reported-by: KASAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-12 12:53:05 +01:00
Michael Kerrisk d1329af1f3 signal-safety.7, signal.7: Migrate discussion of async-signal-safe functions to new page 
Also:
* add more detail on changes across standards
* provide proper section cross references in function references

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-12 12:53:05 +01:00
Michael Kerrisk 6eb174c60d Changes.old: tfix in 4.09 changes 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2016-12-12 12:26:05 +01:00
Michael Kerrisk f9c14f17ba Start of man-pages-4.10: updating Changes and Changes.old 2016-12-12 11:50:11 +01:00