Michael Kerrisk (man-pages | 31 Mar 11:59 2015
Picon

man-pages-3.82 released

Gidday,

The Linux man-pages maintainer proudly announces:

    man-pages-3.82 - man pages for Linux

Tarball download:
    http://www.kernel.org/doc/man-pages/download.html
Git repository:
    https://git.kernel.org/cgit/docs/man-pages/man-pages.git/
Online changelog:
    http://man7.org/linux/man-pages/changelog.html#release_3.80

A short summary of the release is blogged at:
http://linux-man-pages.blogspot.com/2015/03/man-pages-382-is-released.html

The current version of the pages is browsable at:
http://man7.org/linux/man-pages/

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)

Heinrich Schuchardt | 29 Mar 21:13 2015
Picon
Picon

[PATCH 1/1] futex.2: explanation of blocking

Use shorter sentences.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@...>
---
 man2/futex.2 | 18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/man2/futex.2 b/man2/futex.2
index dea50ea..6a4d45c 100644
--- a/man2/futex.2
+++ b/man2/futex.2
 <at>  <at>  -85,14 +85,18  <at>  <at>  In the uncontended case,
 a thread can access or modify the lock state with atomic instructions,
 for example atomically changing it from not acquired to acquired
 using an atomic compare-and-exchange instruction.
-If a thread cannot acquire a lock because
-it is already acquired by another thread,
-it can request to block if and only the lock is still acquired by
-using the lock's flag as futex word and expecting a value that
-represents the acquired state.
+A thread maybe unable acquire a lock because
+it is already acquired by another thread.
+It then may pass the lock's flag as futex word and the value
+representing the acquired state as expected value to a
+.BR futex ()
+wait operation.
+.BR futex ()
+will block if and only if the lock is still acquired.
 When releasing the lock, a thread has to first reset the
-lock state to not acquired and then execute the futex operation that
(Continue reading)

Heinrich Schuchardt | 29 Mar 20:48 2015
Picon
Picon

[PATCH 1/1] futex.2: explanation of blocking behavior

Shorten overlong sentence.
Highlight futex().
Tfix.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@...>
---
 man2/futex.2 | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/man2/futex.2 b/man2/futex.2
index 0644fc6..dea50ea 100644
--- a/man2/futex.2
+++ b/man2/futex.2
 <at>  <at>  -59,16 +59,18  <at>  <at>  in separate processes may be different,
 the same physical address may be shared by the processes using
 .BR mmap (2).)

-When executing a futex operation that requests to block a thread,
+When executing a
+.BR futex ()
+operation that requests to block a thread,
 the kernel will only block if the futex word has the value that the
 calling thread supplied as expected value.
 The load from the futex word, the comparison with
 the expected value,
 and the actual blocking will happen atomically and totally
-ordered with respect to concurrently executing futex operations
-on the same futex word,
-such as operations that wake threads blocked on this futex word.
-Thus, the futex word is used to connect the synchronization in user spac
(Continue reading)

Heinrich Schuchardt | 29 Mar 20:38 2015
Picon
Picon

[PATCH] futex.2: clarify address mapping

Using the word "physical" address should make the text easier to
make.

Avoid negations like "may not be equal".

Signed-off-by: Heinrich Schuchardt <xypron.glpk@...>
---
 man2/futex.2 | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/man2/futex.2 b/man2/futex.2
index b4a52b1..0644fc6 100644
--- a/man2/futex.2
+++ b/man2/futex.2
 <at>  <at>  -54,12 +54,10  <at>  <at>  The condition is represented by the futex word, which is an address
 in memory supplied to the
 .BR futex ()
 system call, and the value at this memory location.
-(While the virtual addresses for the same memory in separate
-processes may not be equal,
-the kernel maps them internally so that the same memory mapped
-in different locations will correspond for
-.BR futex ()
-calls.)
+(While the virtual addresses for the same physical memory address
+in separate processes may be different,
+the same physical address may be shared by the processes using
+.BR mmap (2).)

 When executing a futex operation that requests to block a thread,
(Continue reading)

Heinrich Schuchardt | 29 Mar 20:23 2015
Picon
Picon

[PATCH] futex.2: tfix

Signed-off-by: Heinrich Schuchardt <xypron.glpk@...>
---
 man2/futex.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man2/futex.2 b/man2/futex.2
index 0959ca0..b4a52b1 100644
--- a/man2/futex.2
+++ b/man2/futex.2
 <at>  <at>  -44,7 +44,7  <at>  <at>  system call provides a method for waiting until a certain condition becomes
 true.
 It is typically used as a blocking construct in the context of
 shared-memory synchronization: The program implements the majority of
-the synchronization in user space, and uses one of operations of
+the synchronization in user space, and uses one of the operations of
 the system call when it is likely that it has to block for
 a longer time until the condition becomes true.
 The program uses another operation of the system call to wake
--

-- 
2.1.4

--
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

Zhen Ren | 27 Mar 06:27 2015

"man 3 vsprintf" : simple bug in EXAMPLE section

Hi,
There is simple bug in EXAMPLE section of "man 3 vsprintf".

Function will return nothing if  it steps into the last "else {}".

------------------ example code -----------------
 char *
       make_message(const char *fmt, ...)
       {
           int n;
           int size = 100;     /* Guess we need no more than 100 bytes */
           char *p, *np;
           va_list ap;
.
cut off
.
               np = realloc(p, size);
               if (np == NULL) {
                   free(p);
                   return NULL;
               } else {
                   p = np;
+                return p;
               }
           }
       }
------------------------------------------------

--
Best regards,
(Continue reading)

Scot Doyle | 26 Mar 13:38 2015

Incorrect commit attribution?

Does commit e8db1b97ebec have incorrect attribution?
--
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

Marian Marinov | 26 Mar 01:28 2015

[PATCH] [patch] mount.2: Add MS_REC description


Signed-off-by: Marian Marinov <mm@...>
---
  man2/mount.2 | 9 +++++++++
  1 file changed, 9 insertions(+)

diff --git a/man2/mount.2 b/man2/mount.2
index b081ba1..0c7b3e9 100644
--- a/man2/mount.2
+++ b/man2/mount.2
 <at>  <at>  -145,6 +145,15  <at>  <at>  was also ignored
  (the bind mount has the same mount options as
  the underlying mount point).
  .TP
+.B MS_REC
+.\" information collected from tools/testing/selftests/mount/unprivileged-remount-test.c
+.\" and include/uapi/linux/fs.h
+This option is used together with
+.BR MS_BIND
+to make the mount recursive. This means that the kernel will walk trough
+all mount points within the source of the BIND and mount all of them in
+the corresponding directories within the destination of the BIND.
+.TP
  .BR MS_DIRSYNC " (since Linux 2.5.19)"
  Make directory changes on this filesystem synchronous.
  (This property can be obtained for individual directories
--

-- 
1.8.4
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
(Continue reading)

Zeng Linggang | 25 Mar 09:14 2015

[PATCH] asprintf.3: ATTRIBUTES: Note functions those are thread-safe

The markings match glibc markings.

Signed-off-by: Zeng Linggang <zenglg.jy@...>
Signed-off-by: Ma Shimiao <mashimiao.fnst@...>
---
 man3/asprintf.3 | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/man3/asprintf.3 b/man3/asprintf.3
index f8f9a9b..981126c 100644
--- a/man3/asprintf.3
+++ b/man3/asprintf.3
 <at>  <at>  -58,6 +58,20  <at>  <at>  If memory allocation wasn't possible, or some other error occurs,
 these functions will return \-1, and the contents of
 .I strp
 is undefined.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw23 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR asprintf (),
+.BR vasprintf ()
+T}	Thread safety	MT-Safe locale
+.TE
+
(Continue reading)

Zeng Linggang | 25 Mar 04:15 2015

[PATCH v2] getutent.3: ATTRIBUTES: Note functions those aren't thread-safe

The markings match glibc markings.

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

diff --git a/man3/getutent.3 b/man3/getutent.3
index 4ff5581..3365382 100644
--- a/man3/getutent.3
+++ b/man3/getutent.3
 <at>  <at>  -155,6 +155,46  <at>  <at>  functions can also fail for the reasons described in
 /var/run/utmp	database of currently logged-in users
 .br
 /var/log/wtmp	database of past user logins
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lb lb lbw28
+l l l.
+Interface	Attribute	Value
+T{
+.BR getutent ()
+T}	Thread safety	T{
+MT-Unsafe init race:utent
+.br
+race:utentbuf sig:ALRM timer
+T}
(Continue reading)

bugzilla | 24 Mar 14:02 2015

[Bug 95421] New: Outdated documentation on posix_fadvise?

https://bugzilla.kernel.org/show_bug.cgi?id=95421

            Bug ID: 95421
           Summary: Outdated documentation on posix_fadvise?
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
          Assignee: documentation_man-pages@...
          Reporter: maik@...
        Regression: No

http://man7.org/linux/man-pages/man2/posix_fadvise.2.html suggests that
POSIX_FADV_DONTNEED has no effect on dirty pages. However, if I'm reading
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/mm/fadvise.c?id=v3.19#n115
correctly, it will in fact schedule dirty pages for writeout if the underlying
device is not already congested.

Can you please verify actual behavior and update the manpage if indicated?

--

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@...
(Continue reading)


Gmane