Peter Schiffer | 23 Apr 13:58 2014
Picon

[patch] set_mempolicy.2: wfix

Hi Michael,

sending minor wording fix for set_mempolicy(2) man page.

peter

Attachment (set_mempolicy.2.patch): text/x-patch, 396 bytes
Peter Schiffer | 22 Apr 19:21 2014
Picon

[patch] open.2: Update note about the alignment of the user buffer and the file offset for O_DIRECT flag

Hello Michael,

the sentence in open(2) man page in notes for O_DIRECT flag:
"Under Linux 2.6, alignment to 512-byte boundaries suffices."

is not universally correct. The alignment is a property of the storage, 
for example, 4k-sector drives with no 512 byte sector emulation will be 
unable to perform 512-byte direct I/O.

The patch clarifies this sentence.

Thanks,

peter
Attachment (open.2.patch): text/x-patch, 695 bytes
Carsten Andrich | 22 Apr 18:01 2014
Picon
Picon

[patch] packet.7: PACKET_LOSS has inverse meaning

Hey there,

I stumbled upon an error in packet.7 regarding the meaning of the
PACKET_LOSS socket option. According to the current git version of
linux-man setting PACKET_LOSS causes malformed packets to *not* be
silently dropped.

However it is the other way round. If PACKET_LOSS is *not* set,
malformed packets will be marked TP_STATUS_WRONG_FORMAT and the
transmission process aborted, leaving untransmitted packets in the ring.
If it *is* set, malformed packets will be silently skipped, their status
set to TP_STATUS_AVAILABLE and the transmission process continued with
the following packet.

This behaviour can be clearly seen in net/packet/af_packet.c:
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/net/packet/af_packet.c#n2300

The value accompanying TP_PACKET_LOSS translates into po->tp_loss:
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/net/packet/af_packet.c#n3304

I inverted the meaning of PACKET_LOSS and clarified the description in
the attached patch.

Cheers,
Carsten.

Attachment (packet.7.patch): text/x-patch, 1210 bytes
Peng Haitao | 21 Apr 11:17 2014

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

The functions pthread_attr_setstack() and pthread_attr_getstack()
are thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/pthread_attr_setstack.3 | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/man3/pthread_attr_setstack.3 b/man3/pthread_attr_setstack.3
index 0830479..e6ebb9f 100644
--- a/man3/pthread_attr_setstack.3
+++ b/man3/pthread_attr_setstack.3
 <at>  <at>  -23,7 +23,7  <at>  <at> 
 .\" the source, must acknowledge the copyright and authors of this work.
 .\" %%%LICENSE_END
 .\"
-.TH PTHREAD_ATTR_SETSTACK 3 2008-10-24 "Linux" "Linux Programmer's Manual"
+.TH PTHREAD_ATTR_SETSTACK 3 2014-04-21 "Linux" "Linux Programmer's Manual"
 .SH NAME
 pthread_attr_setstack, pthread_attr_getstack \- set/get stack
 attributes in thread attributes object
 <at>  <at>  -109,6 +109,13  <at>  <at>  and
 is not both readable and writable by the caller.
 .SH VERSIONS
 These functions are provided by glibc since version 2.2.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR pthread_attr_setstack ()
+and
(Continue reading)

Peng Haitao | 21 Apr 10:14 2014

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

The functions pthread_attr_setscope() and pthread_attr_getscope()
are thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/pthread_attr_setscope.3 | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/man3/pthread_attr_setscope.3 b/man3/pthread_attr_setscope.3
index e52fe5d..2effe6b 100644
--- a/man3/pthread_attr_setscope.3
+++ b/man3/pthread_attr_setscope.3
 <at>  <at>  -23,7 +23,7  <at>  <at> 
 .\" the source, must acknowledge the copyright and authors of this work.
 .\" %%%LICENSE_END
 .\"
-.TH PTHREAD_ATTR_SETSCOPE 3 2013-04-19 "Linux" "Linux Programmer's Manual"
+.TH PTHREAD_ATTR_SETSCOPE 3 2014-04-21 "Linux" "Linux Programmer's Manual"
 .SH NAME
 pthread_attr_setscope, pthread_attr_getscope \- set/get contention scope
 attribute in thread attributes object
 <at>  <at>  -116,6 +116,13  <at>  <at>  An invalid value was specified in
 specified the value
 .BR PTHREAD_SCOPE_PROCESS ,
 which is not supported on Linux.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR pthread_attr_setscope ()
+and
(Continue reading)

Peng Haitao | 21 Apr 07:51 2014

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

The functions pthread_attr_setschedpolicy() and
pthread_attr_getschedpolicy() are thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/pthread_attr_setschedpolicy.3 | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/man3/pthread_attr_setschedpolicy.3 b/man3/pthread_attr_setschedpolicy.3
index fbd37ca..794aa92 100644
--- a/man3/pthread_attr_setschedpolicy.3
+++ b/man3/pthread_attr_setschedpolicy.3
 <at>  <at>  -23,7 +23,7  <at>  <at> 
 .\" the source, must acknowledge the copyright and authors of this work.
 .\" %%%LICENSE_END
 .\"
-.TH PTHREAD_ATTR_SETSCHEDPOLICY 3 2013-06-21 "Linux" "Linux Programmer's Manual"
+.TH PTHREAD_ATTR_SETSCHEDPOLICY 3 2014-04-21 "Linux" "Linux Programmer's Manual"
 .SH NAME
 pthread_attr_setschedpolicy, pthread_attr_getschedpolicy \- set/get
 scheduling policy attribute in thread attributes object
 <at>  <at>  -97,6 +97,13  <at>  <at>  error ("attempt was made to set the attribute to an unsupported value") for
 .BR pthread_attr_setschedpolicy ().
 .\" .SH VERSIONS
 .\" Available since glibc 2.0.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR pthread_attr_setschedpolicy ()
+and
(Continue reading)

Peng Haitao | 21 Apr 05:29 2014

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

The functions pthread_attr_setschedparam() and
pthread_attr_getschedparam() are thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/pthread_attr_setschedparam.3 | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/man3/pthread_attr_setschedparam.3 b/man3/pthread_attr_setschedparam.3
index 6d84f5d..49d1e4d 100644
--- a/man3/pthread_attr_setschedparam.3
+++ b/man3/pthread_attr_setschedparam.3
 <at>  <at>  -23,7 +23,7  <at>  <at> 
 .\" the source, must acknowledge the copyright and authors of this work.
 .\" %%%LICENSE_END
 .\"
-.TH PTHREAD_ATTR_SETSCHEDPARAM 3 2013-06-21 "Linux" "Linux Programmer's Manual"
+.TH PTHREAD_ATTR_SETSCHEDPARAM 3 2014-04-21 "Linux" "Linux Programmer's Manual"
 .SH NAME
 pthread_attr_setschedparam, pthread_attr_getschedparam \- set/get
 scheduling parameter attributes in thread attributes object
 <at>  <at>  -97,6 +97,13  <at>  <at>  On Linux these functions always succeed
 handle a possible error return).
 .\" .SH VERSIONS
 .\" Available since glibc 2.0.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR pthread_attr_setschedparam ()
+and
(Continue reading)

Peng Haitao | 21 Apr 03:20 2014

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

The functions pthread_attr_setinheritsched() and
pthread_attr_getinheritsched() are thread safe.

Signed-off-by: Peng Haitao <penght@...>
---
 man3/pthread_attr_setinheritsched.3 | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/man3/pthread_attr_setinheritsched.3 b/man3/pthread_attr_setinheritsched.3
index 5a0c9ac..c760781 100644
--- a/man3/pthread_attr_setinheritsched.3
+++ b/man3/pthread_attr_setinheritsched.3
 <at>  <at>  -23,7 +23,7  <at>  <at> 
 .\" the source, must acknowledge the copyright and authors of this work.
 .\" %%%LICENSE_END
 .\"
-.TH PTHREAD_ATTR_SETINHERITSCHED 3 2013-04-19 "Linux" "Linux Programmer's Manual"
+.TH PTHREAD_ATTR_SETINHERITSCHED 3 2014-04-21 "Linux" "Linux Programmer's Manual"
 .SH NAME
 pthread_attr_setinheritsched, pthread_attr_getinheritsched \- set/get
 inherit-scheduler attribute in thread attributes object
 <at>  <at>  -107,6 +107,13  <at>  <at>  error ("attempt was made to set the attribute to an unsupported value") for
 .BR pthread_attr_setinheritsched ().
 .\" .SH VERSIONS
 .\" Available since glibc 2.0.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR pthread_attr_setinheritsched ()
+and
(Continue reading)

Michael Kerrisk (man-pages | 20 Apr 20:48 2014
Picon

man-pages-3.65 released

Gidday,

The Linux man-pages maintainer proudly announces:

    man-pages-3.65 - 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.65

A short summary of the release is blogged at:
http://linux-man-pages.blogspot.com/2014/04/man-pages-365-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 | 20 Apr 12:28 2014
Picon
Picon

munmap, msync: synchronization

Hello Michael,

when analyzing how the fanotify API interacts with mmap(2) I stumbled 
over the following issues in the manpages:

The manpage of msync(2) says:
"msync() flushes changes made to the in-core copy of a file that was 
mapped into memory using mmap(2) back to disk."

"back to disk" implies that the file system is forced to actually write 
to the hard disk, somewhat equivalent to invoking sync(1). Is that 
guaranteed for all file systems?

Not all file systems are necessarily disk based (e.g. davfs, tmpfs).

So shouldn't we write:
"... back to the file system."

http://pubs.opengroup.org/onlinepubs/007904875/functions/msync.html
says
"... to permanent storage locations, if any,"

The manpage of munmap(2) leaves it unclear, if copying back to the 
filesystem is synchronous or asynchronous.
This bit of information is important, because, if munmap is 
asynchronous, applications might want to call msync(,,MS_SYNC), before 
calling munmap. If munmap is synchronous it might block until the file 
system responds (think of waiting for a tape to be loaded, or a webdav 
server to respond).

(Continue reading)

Yuri Kozlov | 20 Apr 06:41 2014
Picon

[PATCH] timer_getoverrun.2:tfix

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

diff --git a/man2/timer_getoverrun.2 b/man2/timer_getoverrun.2
index d64255a..c14230b 100644
--- a/man2/timer_getoverrun.2
+++ b/man2/timer_getoverrun.2
 <at>  <at>  -78,7 +78,7  <at>  <at>  Timer overruns can also occur when expiration notifications
 are delivered via invocation of a thread,
 since there may be an arbitrary delay between an expiration of the timer
 and the invocation of the notification thread,
-and in that delay interval, additional timer expirations may occur
+and in that delay interval, additional timer expirations may occur.
 .SH RETURN VALUE
 On success,
 .BR timer_getoverrun ()
--

-- 
1.9.1

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