Carlos O'Donell [Fri, 16 Jan 2015 03:18:33 +0000 (22:18 -0500)]
getmntent.3: Consistency fix: use "stream" as name for "FILE *" argument
Harmonize all the manual pages to use "stream" for FILE*
instead of randomly using "fp" or "stream." Choosing something
and being consistent helps users scan the man pages quickly
and understand what they are looking at.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Carlos O'Donell [Fri, 16 Jan 2015 03:18:26 +0000 (22:18 -0500)]
getpwent_r.3: Consistency fix: use "stream" as name for "FILE *" argument
Harmonize all the manual pages to use "stream" for FILE*
instead of randomly using "fp" or "stream." Choosing something
and being consistent helps users scan the man pages quickly
and understand what they are looking at.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Carlos O'Donell [Fri, 16 Jan 2015 03:18:21 +0000 (22:18 -0500)]
getspnam.3: Consistency fix: use "stream" as name for "FILE *" argument
Harmonize all the manual pages to use "stream" for FILE*
instead of randomly using "fp" or "stream." Choosing something
and being consistent helps users scan the man pages quickly
and understand what they are looking at.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Carlos O'Donell [Fri, 16 Jan 2015 03:18:16 +0000 (22:18 -0500)]
getgrent_r.3: Consistency fix: use "stream" as name for "FILE *" argument
Harmonize all the manual pages to use "stream" for FILE*
instead of randomly using "fp" or "stream." Choosing something
and being consistent helps users scan the man pages quickly
and understand what they are looking at.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Carlos O'Donell [Fri, 16 Jan 2015 03:18:29 +0000 (22:18 -0500)]
malloc_info.3: Consistency fix: use "stream" as name for "FILE *" argument
Harmonize all the manual pages to use "stream" for FILE*
instead of randomly using "fp" or "stream." Choosing something
and being consistent helps users scan the man pages quickly
and understand what they are looking at.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Carlos O'Donell [Fri, 16 Jan 2015 03:18:24 +0000 (22:18 -0500)]
putgrent.3: Consistency fix: use "stream" as name for "FILE *" argument
Harmonize all the manual pages to use "stream" for FILE*
instead of randomly using "fp" or "stream." Choosing something
and being consistent helps users scan the man pages quickly
and understand what they are looking at.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Carlos O'Donell [Fri, 16 Jan 2015 03:18:18 +0000 (22:18 -0500)]
fclose.3: Consistency fix: use "stream" as name for "FILE *" argument
Harmonize all the manual pages to use "stream" for FILE*
instead of randomly using "fp" or "stream." Choosing something
and being consistent helps users scan the man pages quickly
and understand what they are looking at.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Dave Hansen [Sat, 10 Jan 2015 14:03:47 +0000 (15:03 +0100)]
prctl.2: Add description of Intel MPX calls
The 3.19 kernel will have support for Intel MPX, including
a pair of new prctl() calls (PR_MPX_ENABLE_MANAGEMENT and
PR_MPX_DISABLE_MANAGEMENT) for enabling and disabling the
kernel's management of the "bounds tables". Add a
descriptions of the interface.
The kernel patches were written by myself and another Intel
developer.
Signed-off-by: Dave Hansen <dave.hansen@intel.com> Cc: Qiaowei Ren <qiaowei.ren@intel.com> Cc: linux-man@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Vince Weaver [Thu, 8 Jan 2015 17:04:30 +0000 (12:04 -0500)]
perf_event_open.2: Clarify the PERF_FLAG_FD_* flags
This change clarifies the behavior of the PERF_FLAG_FD_OUTPUT and
PERF_FLAG_FD_NO_GROUP flags to perf_event_open(), and removes
the related FIXME comments.
While writing tests to validate the behavior of these flags I
discovered that PERF_FLAG_FD_OUTPUT has been broken since the
2.6.35 kernel release.
Signed-off-by: Vince Weaver <vincent.weaver@maine.edu> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Michael Kerrisk [Wed, 7 Jan 2015 12:39:33 +0000 (13:39 +0100)]
seccomp.2: srcfix: Remove a FIXME
Quoting Daniel's response to my FIXME
> Still hoping to hear from Will Drewy regarding this FIXME in the
> page source:
>
> .\" FIXME What is the significance of the line
> .\" ftest->code = BPF_LDX | BPF_W | BPF_ABS;
> .\" in kernel/seccomp.c::seccomp_check_filter()?
This came in from our rework via commit bd4cf0ed331a ("net: filter:
rework/optimize internal BPF interpreter's instruction set"), and
is kernel-internal only, and unused in classic BPF. It translates
into A = *(u32 *) (ctx + K) and will basically load an offset from
the populated seccomp_data (= ctx) to A. For the man-page itself
it has therefore no relevance, hope that clarifies it.
Reviewed-by: Daniel Borkmann <dborkman@redhat.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Michael Kerrisk [Tue, 30 Dec 2014 11:42:30 +0000 (12:42 +0100)]
seccomp.2: Rename arguments inside example program
Rename the arguments to install_filter() to improve readability
a little and to remove a little ambiguity. In particular, rename
'arch' to 't_arch' so that it does not get confused with the
seccomp_data field of the same name.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
projects / thirdparty / man-pages.git / log
