aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2016-10-07cgroups.7: Rework discussion of mounting v1 controllersMichael Kerrisk1-29/+42
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07cgroups.7: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07cgroups.7: Prefer "controller" over "subsystem"Michael Kerrisk1-19/+19
Replace various uses of "subsystem" with "controller". The former too was originally used in describing cgroups, but it is vague to the point of ambiguity. The latter term is a little less ambiguous. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07cgroups.7: Note that a controller can't be simultaneously used in v1 and v2Michael Kerrisk1-0/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07cgroups.7: Minor rewordingMichael Kerrisk1-5/+4
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07cgroups.7: Rework intro text a littleMichael Kerrisk1-39/+43
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07cgroups.7: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07cgroups.7: Use "threads" rather than "tasks" in descriptionMichael Kerrisk1-40/+39
Users-space programmers generally consider things in terms of "processes" and threads". Update the text to remove most uses of the term "tasks". Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07cgroups.7: wfix: fix reference to a kernel source fileMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07cgroups.7: Remove some redundant text on /proc filesMichael Kerrisk1-9/+2
The /proc files were mentioned in two different places. Once is enough. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07proc(5): ffixMike Frysinger1-3/+3
2016-10-07getrusage.2, madvise.2, memfd_create.2, mlock.2, mount.2, getauxval.3, ↵Michael Kerrisk11-16/+16
core.5, capabilities.7, pid_namespaces.7, symlink.7, user_namespaces.7: Consistently use /proc/[pid] (not /proc/PID) Reported-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07adjtimex.2: Fix kernel version referencesNikola Forró1-3/+3
ADJ_SETOFFSET mode was added in 2.6.39: $ git tag --contains 094aa1881fdc1b8889b442eb3511b31f3ec2b762 | head -n 1 v2.6.39 ADJ_MICRO and ADJ_NANO modes were added in 2.6.26: $ git tag --contains eea83d896e318bda54be2d2770d2c5d6668d11db | head -n 1 v2.6.26 Signed-off-by: Nikola Forró <nforro@redhat.com>
2016-10-07proc.5: srcfixMichael Kerrisk1-0/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07core.5: Tweaks to Mike Frysinger's patchMichael Kerrisk1-16/+12
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07core(5): Add more details for output paths and the crash handlerMike Frysinger1-0/+34
People sometimes assume that the crash handler runs in the same context as the crashing process. They would be incorrect :). Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2016-10-07proc.5: Document /proc/PID/seccompMichael Kerrisk1-0/+24
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07proc.5: wfixMichael Kerrisk1-2/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07proc.5: Expand discussion of /proc/[pid]/rootMichael Kerrisk1-0/+34
Add a shell example showing that /proc/[pid]/root is more than a symlink. Based on an example provided by Mike Frysinger in an earlier commit message. Cowritten-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07proc.5: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07proc(5): Clarify the root symlink and mount namespacesMike Frysinger1-0/+4
If the target process is in a different mount namespace, the root symlink actually shows that view of the filesystem. As an example: /* Terminal 1 */ $ unshare -Urnm # mount -t tmpfs tmpfs /etc # mount --bind /bin /dev # echo $$ 17168 /* Terminal 2 */ # ls /etc # Normal view of /etc files. # ls /proc/17168/root/etc # Empty view of the tmpfs. # ls /dev # Normal view of /dev files. # ls /proc/17168/root/dev # Contents of /bin files. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
2016-10-07wcstombs.3: wcsrtombs() does not provide thread-safe interface to same ↵Michael Kerrisk1-2/+1
functionality As noted in the Debian bug: In "man wcstombs" the words The function wcsrtombs(3) provides a thread safe interface to the same functionality. should be changed to The function wcsrtombs(3) provides a better interface to the same functionality. Because 1) wcsrtombs is not thread safe if "ps" is NULL (see "ATTRIBUTES" in "man wcsrtombs") 2) wcstombs *is* thread safe (see "ATTRIBUTES" in "man wcstombs") 3) "man mbstowcs" says "The function mbsrtowcs(3) provides a better interface to the same functionality." in the same NOTES section. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741360 Reported-by: Igor Liferenko <igor.liferenko@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07wcsrtombs.3: ffixMichael Kerrisk1-6/+6
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07wcstombs.3: ffixMichael Kerrisk1-6/+7
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07nanosleep.2: wfix: rework some text around historical behaviorMichael Kerrisk1-2/+1
Referring to "current" Linux 2.4 kernels is strange... Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07nanosleep.2: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07getunwind.2: Simplify text referring to vdso(7)Michael Kerrisk1-6/+2
The detail given here is redundant, since this info is also in vdso(7). Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07getumask.3: Point to umask(2) for a thread-safe way to discover process's umaskMichael Kerrisk1-0/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07getumask.3: fMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07getumask.3: Note that getumask() is still unavailable in glibc 2.24Michael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07semctl.2: wfix: CONFORMING TO: change a POSIX.1-2001 to POSIX.1-2008Bill Pemberton1-1/+1
The section had POSIX.1-2001 listed twice in a row instead of POSIX.1-2001 and POSIX.1-2008 Signed-off-by: Bill Pemberton <wfp5p@worldbroken.com>
2016-10-07Changes.old: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07open.2: F2FS support for O_TMPFILE was added in Linux 3.16Michael Kerrisk1-2/+5
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07keyctl.2: updates regarding command usage, return values and error codesEugene Syromyatnikov1-51/+568
Hello. I've drafted some updates to the keyctl.2 man page while preparing test for strace syscall decoder. It is focused mostly on description of argument format used in various commands and return values/error codes. Information is based on Documentation/security/keys.txt, include/uapi/linux/keyctl.h, and source code and comments in security/keys/ (mostly comments from security/keys/keyctl.c). Hope you find it useful.
2016-10-07clone.2: Document raw syscall interfaces on various other architecturesMichael Kerrisk1-14/+48
Reported-by: Josh Triplett <josh@joshtriplett.org> Reviewed-by: Josh Triplett <josh@joshtriplett.org> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-10-07clone.2: Change types for 'ptid' and 'ctid' in syscall prototypesMichael Kerrisk1-2/+2
These types changed from 'void *' to 'int *' back in Linux 3.8. The new types are closer to reality, so just update the page without discussing the history. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-25clone.2: Adjust syscall prototype and expand CLONE_SETTLS descriptionKeno Fischer1-6/+20
The prototype for the system call was added in kernel commit 81f10dad, but looking at the kernel's fork.c, I believe the relevant definition is SYSCALL_DEFINE5(clone, unsigned long, clone_flags, unsigned long, newsp, int __user *, parent_tidptr, int __user *, child_tidptr, unsigned long, tls) so the last argument is the tls argument, not a pt_regs argument. I stumbled upon this while trying to understand CLONE_SETTLS, so I expanded that description a little to cover other architectures. Reviewed-by: Josh Triplett <josh@joshtriplett.org>
2016-09-25pipe.7: Document FIONREADMichael Kerrisk1-0/+15
Reported-by: Patrick McLean <patrickm@gaikai.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-23namespaces.7: tfixMichael Kerrisk1-1/+1
Reported-by: Nikola Forró <nforro@redhat.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-22execve.2: Note that real UID, real GID, and supplementary GIDs are unchangedMichael Kerrisk1-0/+4
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-22fork.2: ffixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-22fork.2: PID of new process also does not match any existing session IDMichael Kerrisk1-1/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-22quotactl.2: wfixMichael Kerrisk1-8/+6
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-22quotactl.2: ffixMichael Kerrisk1-92/+95
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21quotactl.2: Tweaks to Eugene Syromyatnikov's patchesMichael Kerrisk1-91/+124
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21quotactl.2: wfixEugene Syromyatnikov1-3/+3
2016-09-21quotactl.2: Updated information regarding XFS-specific quotactl subcommandsEugene Syromyatnikov1-22/+215
Added information regarding structure definitions used for XFS-specific subcommands, updated flag constants, added information regarding ignored syscall arguments, added notes on usage of kernel UAPI header.
2016-09-21quotactl.2: Updated information regarding disk quota flagsEugene Syromyatnikov1-2/+5
Added information regarding DQF_SYS_FILE flag; updated definition of V1_DQF_RSQUASH, which has been defined privately and defined publicly as DQF_ROOT_SQUASH.
2016-09-21quotactl.2: Additions regarding project quotasEugene Syromyatnikov1-4/+6
Added information regarding presence of project quotas.
2016-09-21dlopen.3: dlmopen() is still broken in glibc 2.24Michael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21prctl.2: Simplify list of cases where "dumpable" attribute is resetMichael Kerrisk1-28/+6
Simplify list of cases that cause dumpable attribute to reset to suid_dumpable: there were two lists that together in effect had many duplicates. Also some minor rewordings. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21prctl.2: Refer to proc(5) for effects of dumpability on ownership of /proc/PID/*Michael Kerrisk1-0/+6
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21prctl.2: Minor fix: add a reference to ptrace(2) for PR_SET_DUMPABLEMichael Kerrisk1-1/+4
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21proc.5: srcfixMichael Kerrisk1-0/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21proc.5: Note that 'suid_dumpable' mode 1 is insecureMichael Kerrisk1-1/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21proc.5: Add reference to core(5) in discussion of 'suid_dumpable'Michael Kerrisk1-0/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21proc.5: Refer to ptrace(2) for info on effect of suid_dumpable on ptraceabilityMichael Kerrisk1-1/+4
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21proc.5: Explain rules determining ownership of /proc/PID/* filesMichael Kerrisk1-0/+22
Describe the effect of the "dumpable" attribute on ownership of /proc/PID files. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21proc.5: wfixMichael Kerrisk1-2/+5
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-21proc.5: Note effect of 'suid_dumpable' on ownership of /proc/PID filesMichael Kerrisk1-0/+4
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-20capabilities.7: SEE ALSO: add proc(5)Michael Kerrisk1-0/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-20epoll_wait.2: Clarify that the timeout is measured against CLOCK_MONOTONICMike Crowe1-0/+3
The existing page left the choice of clock as ambiguous. My reading of the kernel implementation is that CLOCK_MONOTONIC is always used since ep_poll() calls schedule_hrtimeout_range(), which calls schedule_hrtimeout_range_clock() passing CLOCK_MONOTONIC. References: http://lxr.free-electrons.com/source/fs/eventpoll.c?v=4.7#L1614 http://lxr.free-electrons.com/source/kernel/time/hrtimer.c?v=4.7#L1785 The "measured against" terminology was borrowed from nanosleep.2. I've checked all the way back to Linux v2.6.12 where the calculation was done using jiffies so I think that this has effectively always been true. Signed-off-by: Mike Crowe <mac@mcrowe.com>
2016-09-16futex.2: srcfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-16bpf.2: srcfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-16clone.2: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-16lirc.4, proc.5, netlink.7: tfixMichael Kerrisk3-8/+8
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-16proc.5: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-16proc.5: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-16execve.2: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-16prctl.2: ERRORS: Add EACCES error for PR_SET_SECCOMP-SECCOMP_MODE_FILTERMichael Kerrisk1-0/+16
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-15clone.2: EINVAL is generated by glibc wrapper for NULL 'fn' or 'child_stack'Michael Kerrisk1-3/+6
Clarify that this error is produced by the wrapper function, not the underlying system call. In particular, the point is that the raw system call can accommodate a NULL pointer for 'child_stack'. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-15ld.so.8: Clarify text describing whether secure-mode programs preload librariesMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12proc.5: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12proc.5: Minor tweaks to Namhyung Kim's patchMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12proc.5: Add description of CLEAR_REFS_MM_HIWATER_RSSNamhyung Kim1-1/+6
The Linux kernel commit 695f05593693 ("fs/proc/task_mmu.c: add user-space support for resetting mm->hiwater_rss (peak RSS)") added a way to reset peak RSS of a process but missed to update manpage. Cc: Petr Cermak <petrcermak@chromium.org> Acked-by: Petr Cermak <petrcermak@chromium.org> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
2016-09-12raw.7: Clarify user namespace requirements for CAP_NET_RAWMichael Kerrisk1-2/+2
Also remove mention of UID 0 as a method or creating a raw socket. As far as I can tell from reading the kernel source (net/ipv4/af_inet.c), this is not true. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12packet.7: Clarify user namespace requirements for CAP_NET_RAWMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12open.2: Clarify user namespace capability requirements for O_NOATIMEMichael Kerrisk1-2/+15
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12proc.5: Clarify user namespace requirements for /proc/sys/fs/protected_hardlinksMichael Kerrisk1-2/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12bindresvport.3, rcmd.3, ip.7: Note user namespace requirements for ↵Michael Kerrisk3-5/+9
CAP_NET_BIND_SERVICE Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12ip.7: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12msgctl.2, msgget.2, msgop.2, semctl.2, semget.2, semop.2, shmctl.2, ↵Michael Kerrisk9-9/+9
shmget.2, shmop.2: Note the user namespace requirements for CAP_IPC_OWNER Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12chroot.2: Note user namespace requirements for CAP_SYS_CHROOTMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setuid.2: Note user namespace requirements for CAP_SETUIDMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setreuid.2: Note user namespace requirements for CAP_SETUID and CAP_SETGIDMichael Kerrisk1-4/+4
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setresuid.2: Note user namespace requirements for CAP_SETUIDMichael Kerrisk1-2/+11
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setgid.2: Note user namespace requirements for CAP_SETGIDMichael Kerrisk1-1/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setgid.2: ffixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12seteuid.2: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12seteuid.2: Note user namespace requirements for CAP_SETUID and CAP_SETGIDMichael Kerrisk1-13/+16
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setuid.2: wfixMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setresuid.2: wfixMichael Kerrisk1-4/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setgid.2: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12kill.2: Minor wording fixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12kill.2: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12seccomp.2: CAP_SYS_ADMIN is required only in caller's user namespaceMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12getrlimit.2: Note user namespace semantics for CAP_SYS_RESOURCEMichael Kerrisk1-1/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12getgroups.2: Note user namespace requirements for CAP_SETGIDMichael Kerrisk1-5/+5
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12getdomainname.2: Note user namespace requirements for CAP_SYS_ADMINMichael Kerrisk1-2/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12gethostname.2: Note user namespace requirements for CAP_SYS_ADMINMichael Kerrisk1-1/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12prctl.2: Note user namespace requirements for PR_CAPBSET_DROP CAP_SETPCAPMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12reboot.2: Note user namespace requirements around CAP_SYS_BOOTMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12sched_setaffinity.2: Note user namespace requirements for CAP_SYS_NICEMichael Kerrisk1-1/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12kill.2: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12kill.2: srcfixMichael Kerrisk1-3/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12kill.2: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12kill.2: Note the user namespace requirement for CAP_KILLMichael Kerrisk1-1/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12killpg.2: Refer reader to kill(2) for signal permission rulesMichael Kerrisk1-10/+4
Rather than repeating details here, refer the reader to kill(2) (so that the rules are in a canonical location, and need only be edited in one place for future changes--see next commit). Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12fcntl.2: Note an important detail of F_SETOWN permission rules for signalsMichael Kerrisk1-0/+7
F_SETOWN records the caller's credentials at the time of the fcntl() call, and it is these saved credentials that are used for subsequent permission checks. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12socket.7: SIOCSPGRP: refer to fcntl(2) F_SETOWN for correct permission rulesMichael Kerrisk1-12/+6
The permission rules described for SIOCCPGRP are wrong. Rather than repeat the rules here, just refer the reader to fcntl(2), where the rules are described for F_SETOWN. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12close.2: Add mention of the close-on-exec flagMichael Kerrisk1-0/+7
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12umask.2: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12open.2: Clarify the rules about how the group ID of a new file is determinedMichael Kerrisk1-5/+10
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12open.2: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12open.2: ffixMichael Kerrisk1-0/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12getsid.2: Rework description to be somewhat clearerMichael Kerrisk1-4/+12
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setsid.2: Refer to credentials(7) for details for details on controlling ↵Michael Kerrisk1-1/+4
terminal Refer to credentials(7) for details of how a session obtains a controlling terminal. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12getsid.2: wfixMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12getsid.2: Correct the definition of "session ID"Michael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setpgid.2: Minor wording fixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setsid.2: Minor wording fixesMichael Kerrisk1-3/+5
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setpgid.2, setsid.2: Relocate some text on sessions and sessions leadersMichael Kerrisk2-10/+10
Some text that was in setpgid(2) is better placed in setsid(2). Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12setpgid.2: Add a reference to credentials(7)Michael Kerrisk1-0/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12credentials.7: SEE ALSO: add setsid(2) and setpgid(2)Michael Kerrisk1-0/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12execve.2: Mention use of 'environ' to access environment listMichael Kerrisk1-0/+6
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12execve.2: Minor clarificationMichael Kerrisk1-1/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12execve.2: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12execve.2: Minor clarificationMichael Kerrisk1-3/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12execve.2: ffixMichael Kerrisk1-0/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12execve.2: Minor clarificationMichael Kerrisk1-2/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12fcntl.2: Make the description of the effect of close-on-exec a little clearerMichael Kerrisk1-3/+10
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12close.2: Clarify discussion noting that close() does not flush buffer cacheMichael Kerrisk1-4/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-12fcntl.2: Clarify that F_GETFD and F_GETFL return flags via the function resultMichael Kerrisk1-2/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11ld.so.8: Remove mention of "ELF only"Michael Kerrisk1-4/+4
Drawing a distinction between ELF-only features versus a,out ceased to be relevant long ago, so cluttering the page with "ELF-only" serves no purpose. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11ld.so.8: wfixMichael Kerrisk1-17/+17
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11ld.so.8: Remove discussion of environment variables understood by libc5Michael Kerrisk1-29/+1
libc5 disappeared long ago, so cease cluttering up this page with those ancient details. Thus, remove discussion of the following environment variables: LD_AOUT_LIBRARY_PATH, LD_AOUT_PRELOAD, LD_KEEPDIR, LD_NOWARN, and LDD_ARGV0. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11ld.so.8: wfixMichael Kerrisk1-2/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11ld.so.8: Remove text with ancient libc4 and Linux libc detailsMichael Kerrisk1-5/+0
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11ld.so.8: Add glibc version for LD_USE_LOAD_BIASMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11ld.so.8: ffixMichael Kerrisk1-44/+22
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11ld.so.8: Expand description of LD_DEBUGMichael Kerrisk1-3/+40
Provide a list of the categories, and note that multiple categories can be specified. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11ld.so.8: wfixMichael Kerrisk1-4/+5
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11initrd.4: ffixMichael Kerrisk1-0/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11initrd.4: wfixMichael Kerrisk1-1/+0
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11mouse.4: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11mouse.4: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-11lp.4: wfixMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-10proc.5: Clarify description of /proc/PID/statm 'lib' and 'dt' fieldsMichael Kerrisk1-2/+2
These fields are always zero since Linux 2.6. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-10proc.5: Clarify that /proc/PID/statm 'shared' field counts *resident* pagesMichael Kerrisk1-1/+2
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741360 Reported-by: Zefram <zefram@fysh.org> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-10proc.5: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-10proc.5: Document /proc/PID/status 'RssAnon', 'RssFile', and 'RssShmem' fieldsMichael Kerrisk1-0/+24
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-10proc.5: Document /proc/PID/status 'HugetlbPages' fieldMichael Kerrisk1-0/+6
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-10proc.5: Update example VM values in /proc/PID/statusMichael Kerrisk1-13/+13
In preparation for following patches. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-09clone.2: wfixMichael Kerrisk1-2/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-09rtnetlink.3: tfixHuKeping1-1/+1
Signed-off-by: Hu Keping <hukeping@huawei.com>
2016-09-04readv.2: Clarify that RWF_DSYNC and RWF_SYNC apply only to data being writtenMichael Kerrisk1-2/+4
Reported-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-04readv.2: Document the pwritev2() RWF_SYNC and RWF_DSYNC flagsMichael Kerrisk1-0/+18
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-04rename.2: Minor wording fixMichael Kerrisk1-3/+1
The meaning of "when overwriting" is not clear. I believe what is meant is that when an existing 'newpath' is replaced. However, we can convey that meaning by eliding this text with the preceding paragraph, so this patch does that. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-04rename.2: Relocate some text textMichael Kerrisk1-7/+7
Relocate text noting that there may be a window when 'oldpath' and 'newpath' refer to the same file. Logically, this text appears to belong near the text noting that an existing 'newpath' will be atomically replaced. (In ancient versions of the page, these two pieces of text were closer together.) Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-09-04rename.2: Clarify that ERRORS may cause rename to fail (not to be nonatomic)Michael Kerrisk1-2/+4
The existing wording suggests that there are ERRORS that may cause the operation to be nonatomic. The point is of course that there are various restrictions on rename operations that may cause the operation to fail. Reported-by: Tim Savannah <kata198@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-31mlock.2: Minor tweaks to Sebastian Andrzej Siewior's patchMichael Kerrisk1-7/+7
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-31mlock.2: Document that fork() after mlock() may be a bad idea in a RT processSebastian Andrzej Siewior1-0/+14
fork() will remove the write PTE bit from the page table on each VMA which will be copied via COW. As such, the memory is available but marked read only in the page table and will fault on write access. This renders the previous mlock() operation almost useless because in a multithreaded application a realtime thread may block on mmap_sem while a thread with low priority is holding the mmap_sem (for instance because it is allocating memory which needs to be mapped in). There is actually nothing we can do to mitigate the outcome. We could add a warning to the kernel for people that are not yet aware of the updated documentation. Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
2016-08-31pthread_join.3: Note that the caller might do clean up after joining with a ↵Michael Kerrisk1-0/+3
thread Reported-by: Mats Wichmann <mats@wichmann.us> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-31strverscmp.3: Add an example programMichael Kerrisk1-0/+42
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-31stat.2: Tweak discussion of 'st_size' for /proc and /sys filesMichael Kerrisk1-1/+1
As Mats points out, there appear to be no (or almost no) files under /proc and /sys for which 'st_size' is meaningful. (mtk: verified via some scripting over these directories.) Reported-by: Mats Wichmann <mats@wichmann.us> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-29pthread_join.3: Clarify use of 'retval' pointerMichael Kerrisk1-3/+3
Reported-by: 王守堰 <wangshouyan@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-29stat.2: Improve discussion of 'st_size' for /proc and /sys filesMichael Kerrisk1-5/+13
Reported-by: Ursache Vladimir <f35f22fan@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-29epoll_ctl.2: tfixRuben Kerkhof1-1/+1
2016-08-29epoll_ctl.2: tfixRuben Kerkhof1-1/+1
2016-08-28sigprocmask.2: Minor fixes to Keno Fischer's patchMichael Kerrisk1-5/+5
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-28sigprocmask.2: Expand/clarify libc/kernel sigset_t differenceKeno Fischer1-10/+39
Expand and clarify libc/kernel sigset_t differences. Also move up the signature for rt_sigprocmask, similar to the way this is done in clone.2. Due to the history of sigprocmask, there are various notions of what sigset_t refers to. This attempts to clarify the man page, by giving the major instances different names: - sigset_t is the glibc sigset_t (1024 bits) - kernel_sigset_t is the kernel's sigset_t (64 bits) - old_kernel_sigset_t is the pre-rt kernel's sigset_t (32 bits) and explaining their difference in the NOTES. Even though the sources do not refer to the various sigset_t's by these names, I think it is important to be explicit, esp since sizeof(sigset_t) would give an incorrect value for `sigsetsize` if written in a source file that includes the libc headers. Lastly, move the note on an incorrect `sigsetsize` causing EINVAL up to the ERRORS section, so everything is in one place.
2016-08-28readdir_r(3): tfix: Fix reference to readdir(3)Ruben Kerkhof1-1/+1
2016-08-24clone.2: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-24clone.2: Make the implications of CLONE_FILES more explicitMichael Kerrisk1-4/+5
If CLONE_FILES is not set, the duplicated FDs nevertheless share file offset and status flags via the open file description. Reported-by: Elliott Hughes <enh@google.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-24fcntl.2: Minor wording fix for F_DUPFDMichael Kerrisk1-5/+4
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-23accept.2: tfixMichael Kerrisk1-5/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-23ip.7: wfixMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-23ip.7: tfixMichael Kerrisk1-2/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-23ddp.7: grfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-23ddp.7: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-23fifo.7: wfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-23termcap.5: Minor wording fixesMichael Kerrisk1-7/+8
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-23accept.2: Demote discussion of DECNet to NOTESMichael Kerrisk1-13/+14
DECNet ceased to be important long ago... Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-23accept.2: Mention epoll(7) alongside poll()/select()Michael Kerrisk1-4/+6
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-22fanotify_init.2: Update BUGS informationMichael Kerrisk1-3/+2
Patch 0b37e097a648aa71d4db1ad108001e95b69a2da4 was included in Linux 3.18. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
2016-08-20readlink.2: Make example program handle links that report a size of zeroMichael Kerrisk1-13/+24
Some "magic" symlinks created by the kernel (e.g., those under /proc and /sys) report 'st_size' as zero. Modify the example program to handle that possibility. Reported-by: Ursache Vladimir <f35f22fan@gmail.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-20readlink.2: Emphasize that truncation of returned buffer generates no errorMichael Kerrisk1-1/+4
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-20capabilities.7: Minor tweaks to Matthew Saunders' patchMichael Kerrisk1-5/+7
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-20capabilities.7: Add note about nosuid to file capabilities sectionMichael Kerrisk1-0/+7
2016-08-18makedev.3: tfixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-17cpuset.7: tfixDavid Turner1-1/+1
2016-08-17mmap.2: Small improvement to description of MAP_SHAREDMichael Kerrisk1-2/+3
See https://sourceware.org/bugzilla/show_bug.cgi?id=6887 Reported-by: Siward de Groot <siward@wanadoo.nl> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-17open.2: Minor layout fix in ERRORSMichael Kerrisk1-1/+3
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-17fifo.7: ffixMichael Kerrisk1-1/+1
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-17fcntl.2: ffixMichael Kerrisk1-0/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-12select_tut.2: ffixMichael Kerrisk1-1/+2
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-12ptrace.2: ffixMichael Kerrisk1-1/+1
Reported-by: Sam Varshavchik <mrsam@courier-mta.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2016-08-12select_tut.2: fix issues in examplePeter Wu1-20/+18
Avoid closing cfd if it is -1. Initialize buf1_avail, etc. to avoid uninitialized memory access in the event that accept() fails. Remove redundant setting of nfds. Fix tabs with spaces. Do not try to read/write from/to file descriptors once an existing connection is overwritten, the select() states are stale now. Avoid writing zero bytes from the buffer and then closing the fd. Signed-off-by: Peter Wu <peter@lekensteyn.nl>
2016-08-12resolver.3: Correct arguments to res_ninit(res_state statep)Ray Bellis1-1/+1
The man page for res_ninit() incorrectly says that it takes no parameters, when in fact (and indeed according to the same page further down) it has to take a res_state parameter.
2016-08-12fmemopen.3: Remove bogus suggestion to use setbuffer()Michael Kerrisk1-12/+0
As Rich Felker comments: The stdio buffer associated with the fmemopen-obtained FILE, and the output memory buffer into which it's writing, are conceptually distinct entities, and there is no reason to expect reasonable results if you modify the contents of a setvbuf-associated buffer through other means while it's associated with a FILE. See http://stackoverflow.com/questions/38854163/using-rewind-on-a-file-opened-with-fmemopen Reported-by: Rich Felker <dalias@libc.org> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
generated by cgit 1.2.3-korg (git 2.43.0) at 2025-12-02 03:37:46 +0000