Egmont Koblinger | 26 Apr 13:26 2015

Merge dprintf(3) into printf(3)


I'd like to propose a small change.

I often open the printf(3) manual page, and this beginning with
several variants (fprintf, sprintf...) implicitly suggested me for
many years that this list was kinda complete.  I just randomly came
across dprintf(3) (while visiting

Of course, dprintf(3) is mentioned in the "see also" section of
printf(3), so strictly speaking I should've noticed it much sooner, I
just overlooked it.

I don't find it logical that some printf variations (f, s, sn) are
documented in the same manual page, while another that's not more
different from these (d) is not.

I'd like to recommend refactoring, and integrating dprintf(3) (and
probably asprintf(3) too) in the basic printf(3) manual page.

It's also more useful if "man 3 dprintf" brings up the complete
documentation, rather than just the feature test macros and the
confirmance specification, and points to another manpage for the rest.

Thanks for considering,
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at
(Continue reading)

Webmaster | 23 Apr 20:34 2015

Dear E-mail User

 Dear Email User

 Your Email Password Will Expire In 24 Hours.  Click the link below to login into your account for
confirmation and Upgrade.:

 To Update Your Details.

 Web Admin
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at

bugzilla | 23 Apr 19:07 2015

[Bug 97161] New: bootparam(7): 'debug' parameter: reference to <linux/kernel.h> for information on log levels is misleading.

            Bug ID: 97161
           Summary: bootparam(7): 'debug' parameter: reference to
                    <linux/kernel.h> for information on log levels is
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
          Assignee: documentation_man-pages@...
          Reporter: a.c.kalker@...
        Regression: No

The section on the 'debug' parameter refers the user to <linux/kernel.h> for
more information on kernel log levels, however, that file contains neither a
description of console_loglevel nor nor a description of the various log

The closest I can find is <include/linux/kern_levels.h>, which defines the
various log levels but doesn't explain console_loglevel, Also, it only exists
in recent kernels, version 3.5 and up.
Another candidate would be <include/linux/printk.h>, which does define
console_loglevel but doesn't explain the individual log levels.

Perhaps both references (<include/linux/printk.h>,
(Continue reading)

Zeng Linggang | 23 Apr 06:51 2015

[PATCH] err.3: ATTRIBUTES: Note functions that are thread-safe

The markings match glibc markings.
markings of functions in glibc are:
- err:    MT-Safe locale
- err:    MT-Safe locale
- errx:   MT-Safe locale
- warn:   MT-Safe locale
- warnx:  MT-Safe locale
- verr:   MT-Safe locale
- verrx:  MT-Safe locale
- vwarn:  MT-Safe locale
- vwarnx: MT-Safe locale

Signed-off-by: Zeng Linggang <zenglg.jy@...>
 man3/err.3 | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/man3/err.3 b/man3/err.3
index 783d60a..14eb6e5 100644
--- a/man3/err.3
+++ b/man3/err.3
 <at>  <at>  -106,6 +106,29  <at>  <at>  and
 .BR verrx ()
 functions do not return, but exit with the value of the argument
 .IR eval .
+For an explanation of the terms used in this section, see
+.BR attributes (7).
(Continue reading)

Michael Kerrisk (man-pages | 22 Apr 10:55 2015

Moving attr(5) man page to man-pages

Hi Andreas,

As we discussed offlist, it makes sense to have the attr(5) man 
page in man-pages, rather than as part of the 'attr' project 
documentation, since it mostly relates to kernel details.

So, I'll adopt this page for the next man-pages release; I've
just now copied the latest version from the 'attr' repo. Could
you please take whatever steps are needed ensure that page 
conflicts do not result for downstreams who are taking man 
page feeds from both projects.

I'll move this page into Section 7, since that's where overview
type pages such as this are normally placed in man-pages, but 
I'll also create a link in Section 5, so that acl(5) references
will continue to work.

I've made a number of edits to the page. Some of these were just 
to bring the page closer to man-pages style, but others were to
amend incorrect technical details and add new details. I'd be
pleased if you checked over these commits:

d8ba769 attr.7: File capabilities are implemented using *security* attributes
03a93c3 attr.7: Clarify permissions required to work with 'user' EAs
6ad46a9 attr.7: The ext[234] block limitation applies to sum of all EAs
6db035a attr.7: Document VFS-imposed limits on EAs
edb159d attr.7: Describe limit on EA values for JFS, XFS, and Reiserfs
7f4f24e attr.7: Document EA limits for Btrfs

These changes are already pushed to 'master' at
(Continue reading)

saulery | 22 Apr 02:21 2015

[PATCH 1/3] resolv.conf.5: document use-vc option added to glibc 2.14

From: St├ęphane Aulery <saulery@...>

Fix Ubuntu bug #1110781:

Reported-by: Thomas Hood
Signed-off-by: St├ęphane Aulery <saulery@...>
 man5/resolv.conf.5 | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/man5/resolv.conf.5 b/man5/resolv.conf.5
index f5c8cad..7b6804a 100644
--- a/man5/resolv.conf.5
+++ b/man5/resolv.conf.5
 <at>  <at>  -272,6 +272,13  <at>  <at>  as if it were a top level domain (TLD).
 This option can cause problems if the site has ``localhost'' as a TLD
 rather than having localhost on one or more elements of the search list.
 This option has no effect if neither RES_DEFNAMES or RES_DNSRCH is set.
+.BR use-vc " (since glibc 2.14)"
+.IR _res.options .
+This option forces the usage of TCP for DNS resolutions.
 The \fIdomain\fP and \fIsearch\fP keywords are mutually exclusive.

(Continue reading)

bugzilla | 22 Apr 00:28 2015

[Bug 97051] New: get_mempolicy(2) inconsistent with numaif.h

            Bug ID: 97051
           Summary: get_mempolicy(2) inconsistent with numaif.h
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
          Assignee: documentation_man-pages@...
          Reporter: nyh@...
        Regression: No

get_mempolicy(2)'s synopsis is:

       #include <numaif.h>

       int get_mempolicy(int *mode, unsigned long *nodemask,
                         unsigned long maxnode, unsigned long addr,
                         unsigned long flags);

However, the actual prototype in numif.h (and implementation in numactl's
syscall.c) is subtly different:

       long get_mempolicy(int *policy, const unsigned long *nmask,
                        unsigned long maxnode, void *addr, int flags);

(Continue reading)

Jann Horn | 20 Apr 22:46 2015

[PATCH] stat.2: add note about stat being racy

The same thing was fixed for execve() in commit
8b01fc86b9f425899f8a3a8fc1c47d73c2c20543, but for performance
reasons, that simple patch won't work for stat().
 man2/stat.2 | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/man2/stat.2 b/man2/stat.2
index 0d244af..69ec6a4 100644
--- a/man2/stat.2
+++ b/man2/stat.2
 <at>  <at>  -175,6 +175,29  <at>  <at>  that may be present between some fields on various architectures.
 Consult the glibc and kernel source code
 if you need to know the details.

+\# Background: inode attributes are modified with i_mutex held, but
+\# read by stat() without taking the mutex.
+.I Note:
+For performance and simplicity reasons, different fields in the
+.I stat
+structure may contain state information from different moments
+during the execution of the syscall. For example, if
+.IR st_mode ,
+.IR st_uid
+.IR st_gid
+are changed by another process by calling
+.BR chown (2) ,
+.BR stat ()
+might return the old
(Continue reading)

William Woodruff | 20 Apr 22:41 2015

[PATCH] undocumented.3: remove documented functions

Removed documented functions from undocumented(3).
Applies to 3.83.

Signed-off-by: William Woodruff <william@...>
 man3/undocumented.3 | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/man3/undocumented.3 b/man3/undocumented.3
index a483710..c120639 100644
--- a/man3/undocumented.3
+++ b/man3/undocumented.3
 <at>  <at>  -25,6 +25,7  <at>  <at> 
 .\" 1996-11-08, meem@..., corrections
 .\" 2004-10-31, aeb, changed maintainer address, updated list
+.\" 2015-04-20, william@..., updated list
 .TH UNDOCUMENTED 3 2012-12-21 "Linux" "Linux Programmer's Manual"
 <at>  <at>  -67,8 +68,6  <at>  <at>  for inclusion in the next man page release.
 .BR getdirentries64 (3),
 .BR getmsg (3),
 .BR getnetname (3),
-.BR get_nprocs (3),
-.BR get_nprocs_conf (3),
 .BR get_phys_pages (3),
 .BR getpublickey (3),
 .BR getsecretkey (3),
 <at>  <at>  -79,7 +78,6  <at>  <at>  for inclusion in the next man page release.
(Continue reading)

Michael Kerrisk (man-pages | 20 Apr 07:14 2015

man-pages-3.83 released


The Linux man-pages maintainer proudly announces:

    man-pages-3.83 - man pages for Linux

Tarball download:
Git repository:
Online changelog:

A short summary of the release is blogged at:

The current version of the pages is browsable at:

You are receiving this message either because:

a) You contributed to the content of this release.

b) You are subscribed to linux-man@...

c) I have information (possibly inaccurate) that you are the maintainer
   of a translation of the manual pages, or are the maintainer of the
   manual pages set in a particular distribution, or have expressed
   interest in helping with man-pages maintenance, or have otherwise
   expressed interest in being notified about man-pages releases.
(Continue reading)

Kees Cook | 19 Apr 01:37 2015

Re: [patch] seccomp.2: Note that memory area is read-only

On Mon, Apr 6, 2015 at 8:29 AM, Michael Kerrisk (man-pages)
<mtk.manpages@...> wrote:
> Hi Kees,
> I recently was asked about the point below, and had to go check the code
> to be sure, since the man page said nothing. It would be good to have
> a confirmation: the seccomp_data buffer supplied to a seccomp BPF program
> is read-only, right? (That is, one can't write to the buffer in order to
> change the arguments that a system call actually receives.)

That's correct. If BPF even allows changing the data, it's not copied
back to the syscall when it runs. Anything wanting to do things like
that would need to use ptrace to catch the call an directly modify the
registers before continuing with the call.

> A small man page patch below.

Looks good, thanks!


> Cheers,
> Michael
> --- a/man2/seccomp.2
> +++ b/man2/seccomp.2
>  <at>  <at>  -232,15 +232,15  <at>  <at>  struct sock_filter {            /* Filter block */
(Continue reading)