Jörn Engel | 3 May 02:58 2016

get_mempolicy(2) type mismatch

The manpage seems to have the wrong type for "addr".

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

/usr/include/numaif.h:
extern long get_mempolicy(int *policy, const unsigned long *nmask,
                        unsigned long maxnode, void *addr, int flags);

Jörn

--
The more any quantitative social indicator is used for social decision-making,
the more subject it will be to corruption pressures and the more apt it will
be to distort and corrupt the social processes it is intended to monitor.
-- Campbell's law
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Dr. Tobias Quathamer | 2 May 21:42 2016
Picon

[PATCH] open.2: tfix

---
 man2/open.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man2/open.2 b/man2/open.2
index 0ff0865..012d0c4 100644
--- a/man2/open.2
+++ b/man2/open.2
 <at>  <at>  -1587,7 +1587,7  <at>  <at>  is ignored).
 .BR unlink (2),
 .BR write (2),
 .BR fopen (3),
-.BR acl (5)
+.BR acl (5),
 .BR fifo (7),
 .BR path_resolution (7),
 .BR symlink (7)
--

-- 
2.5.0

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Marko Myllynen | 2 May 13:03 2016
Picon

nsswitch.conf.5: document group merging

Hi,

Here's a patch to document the recently merged glibc group merge
support.

https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=ced8f8933673f4efda1d666d26a1a949602035ed
https://sourceware.org/glibc/wiki/Proposals/GroupMerging

---
 man5/nsswitch.conf.5 | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/man5/nsswitch.conf.5 b/man5/nsswitch.conf.5
index b99f9fd..8b62796 100644
--- a/man5/nsswitch.conf.5
+++ b/man5/nsswitch.conf.5
 <at>  <at>  -204,6 +204,8  <at>  <at>  where
 .B return
 |
 .B continue
+|
+.B merge
 .RE
 .LP
 The ! negates the test, matching all possible results except the
 <at>  <at>  -257,6 +259,16  <at>  <at>  without affecting the search result.
 .TP
 .B continue
 Call the next lookup function.
+.TP
(Continue reading)

Georg Sauthoff | 29 Apr 21:06 2016

prctl() PR_SET_PDEATHSIG race condition note

Hello,

regarding the PR_SET_PDEATHSIG paragraph in prctl(2):

> PR_SET_PDEATHSIG (since Linux 2.1.57)
>       Set the parent death signal of the calling process to arg2
>       (either a signal value in the range 1..maxsig, or 0 to clear).
>       This is the signal that the calling process will get when its
>       parent dies.  This value is cleared for the child of a fork(2)
>       and (since Linux 2.4.36 / 2.6.23) when executing a set-user-ID
>       or set-group-ID binary, or a binary that has associated
>       capabilities (see capabilities(7)).  This value is preserved
>       across execve(2).
>
>       Warning: the "parent" in this case is considered to be the
>       thread that created this process.  In other words, the signal
>       will be sent when that thread terminates (via, for example,
>       pthread_exit(3)), rather than after all of the threads in the
>       parent process terminate.

Perhaps it makes sense to add a note regarding a race condition
between the child being able to call prctl() and an early exit of
the parent process (after a successful fork()); i.e. when the
parent death signal is installed after the parent has already
died.

See for example following links that may indicate that this isn't
necessarily obvious:

- http://lkml.iu.edu/hypermail/linux/kernel/0003.1/0769.html
(Continue reading)

Ed Avis | 28 Apr 18:31 2016

strtod(3) manual page not clear on error handling when endptr is null

strtod(3) says:

>If no conversion is performed, zero is returned and the value of nptr is stored in the location referenced
by endptr.

This surely can't be the case if endptr is null.  I believe that the behaviour is more like

>If no conversion is performed, zero is returned, and (unless endptr is null) the value of nptr is stored in
the location referenced by endptr.

--

-- 
Ed Avis <eda@...>

This email is intended only for the person to whom it is addressed and may contain confidential
information. Any retransmission, copying, disclosure or other use of, this information by persons
other than the intended recipient is prohibited. If you received this email in error, please contact the
sender and delete the material. This email is for information only and is not intended as an offer or
solicitation for the purchase or sale of any financial instrument. Wadhwani Asset Management LLP is a
Limited Liability Partnership registered in England (OC303168) with registered office at 40 Berkeley
Square, 3rd Floor, London, W1J 5AL. It is authorised and regulated by the Financial Conduct Authority.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Nikola Forró | 28 Apr 16:54 2016
Picon

[PATCH] popen.3: RETURN VALUE: describe successful case

Reference:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/popen.html
http://pubs.opengroup.org/onlinepubs/9699919799/functions/pclose.html

Signed-off-by: Nikola Forró <nforro@...>
---
 man3/popen.3 | 25 ++++++++++++++-----------
 1 file changed, 14 insertions(+), 11 deletions(-)

diff --git a/man3/popen.3 b/man3/popen.3
index f075581..bafa42c 100644
--- a/man3/popen.3
+++ b/man3/popen.3
 <at>  <at>  -123,17 +123,18  <at>  <at>  function waits for the associated process to terminate and returns the exit
 status of the command as returned by
 .BR wait4 (2).
 .SH RETURN VALUE
-The
-.BR popen ()
-function returns NULL if the
+.BR popen ():
+on success, returns a pointer to an open stream that
+can be used to read or write to the pipe;
+if the
 .BR fork (2)
 or
 .BR pipe (2)
-calls fail, or if it cannot allocate memory.
-.PP
-The
(Continue reading)

Safeer Pasha | 27 Apr 00:16 2016
Picon

Man page TYPO. 'no pictures attached'

check 'man inxi' and search for 'wron'
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Marko Myllynen | 26 Apr 21:55 2016
Picon

locale.5: Complete LC_COLLATE

Hi,

Here's the first attempt to (almost) complete the locale.5 manual page
by documenting all (but perhaps one) of the missing LC_COLLATE keywords.

I think the LC_COLLATE section is still not enough to be used as the
only source when writing collation rules from scratch but perhaps
that's not even needed, it could be also thought that the section 5
pages merely describe the format used in the files. Naturally more
information could be added later on top of this patch.

Few notes:

- AFAICS coll_weight_max is not used anywhere in glibc
- I'm not aware of any C library implementation on Linux (for which
this manual page would be relevant) which would implement the POSIX
options not supported by glibc
- the glibc specific script keyword could still be documented

Sources:

http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap07.html
http://www.open-std.org/jtc1/SC22/WG20/docs/n972-14652ft.pdf

PS. A couple of unrelated comment clean-ups slipped in as well, sorry
about those.

---
 man5/locale.5 | 45 +++++++++++++++++++++++++++++++--------------
 1 file changed, 31 insertions(+), 14 deletions(-)
(Continue reading)

Colin Ian King | 25 Apr 21:42 2016

aarch64 clone() man page omission

Hi there,

currently, the aarch64 clone() system call requires the stack to be
aligned at a 16 byte boundary, see arch/arm64/kernel/process.c,
copy_thread():

                if (stack_start) {
                        if (is_compat_thread(task_thread_info(p)))
                                childregs->compat_sp = stack_start;
                        /* 16-byte aligned stack mandatory on AArch64 */
                        else if (stack_start & 15)
                                return -EINVAL;
                        else
                                childregs->sp = stack_start;
                }

..and returns -EINVAL if not aligned correctly.  This should be added to
the manual page clone(2) as it took me a while to figure out why clone()
was failing with -EINVAL for aarch64 but not on x86.

Colin
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Nikos Mavrogiannopoulos | 25 Apr 10:48 2016
Picon

[PATCH] Update the random(4) documentation towards a more accurate view on /dev/urandom

This documents the "property" of /dev/urandom of being able to serve numbers
prior to pool being initialized, and removes any suggested usages of /dev/random
which are disputable (i.e., one-time pad).
Document the fact /dev/random is only suitable for applications which can afford
indeterminate delays since very few applications can do so.
Smooth the alarming language about a theoretical attack, and mention that its
security depends on the cryptographic primitives used by the kernel, as well
as the total entropy gathered.

Signed-off-by: Nikos Mavrogiannopoulos <nmav@...>
---
 man4/random.4 | 32 +++++++++++++++++---------------
 1 file changed, 17 insertions(+), 15 deletions(-)

diff --git a/man4/random.4 b/man4/random.4
index b6fdd8c..27a78c6 100644
--- a/man4/random.4
+++ b/man4/random.4
 <at>  <at>  -38,10 +38,10  <at>  <at>  number of bits of noise in the entropy pool.
 From this entropy pool random numbers are created.
 .LP
 When read, the \fI/dev/random\fP device will return random bytes
-only within the estimated number of bits of noise in the entropy
+only within the estimated number of bits of fresh noise in the entropy
 pool.
-\fI/dev/random\fP should be suitable for uses that need very
-high quality randomness such as one-time pad or key generation.
+\fI/dev/random\fP is suitable for uses that need very
+high quality randomness, and can afford indeterminate delays.
 When the entropy pool is empty, reads from \fI/dev/random\fP will block
(Continue reading)

Egmont Koblinger | 23 Apr 23:00 2016
Picon
Gravatar

getlogin(3): mention loginuid

Hi,

I just got to know about /proc/self/loginuid, as well as getlogin(3)
referring to this file prior to utmp, by browsing this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1328947 (esp. comments
13-17 are relevant).

getlogin(3)'s manual page does not mention this at all. (And, for the
record, neither does proc(5), it has a FIXME comment about it).

Could you please fill in this gap?

Thanks a lot,
egmont
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Gmane