Sven Hoexter | 14 Dec 15:20 2014
Picon

[PATCH] proc.5: Add "VmSwap" to /proc/[pid]/status

Documented as is in Documentation/filesystems/proc.txt of Linux 3.18.

Signed-off-by: Sven Hoexter <sven@...>
---
 man5/proc.5 | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/man5/proc.5 b/man5/proc.5
index 96077d0..b16f2a7 100644
--- a/man5/proc.5
+++ b/man5/proc.5
 <at>  <at>  -1587,6 +1587,7  <at>  <at>  VmStk:        88 kB
 VmExe:       572 kB
 VmLib:      1708 kB
 VmPTE:        20 kB
+VmSwap:        0 kB
 Threads:        1
 SigQ:   0/3067
 SigPnd: 0000000000000000
 <at>  <at>  -1672,6 +1673,9  <at>  <at>  Shared library code size.
 .IR VmPTE :
 Page table entries size (since Linux 2.6.10).
 .IP *
+.IR VmSwap :
+Size of swap usage (the number of referred swapents).
+.IP *
 .IR Threads :
 Number of threads in process containing this thread.
 .IP *
--

-- 
(Continue reading)

bugzilla | 11 Dec 03:45 2014

[Bug 89551] New: GNU is frequently spelled Gnu

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

            Bug ID: 89551
           Summary: GNU is frequently spelled Gnu
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: low
          Priority: P1
         Component: man-pages
          Assignee: documentation_man-pages@...
          Reporter: lorenzo567@...
        Regression: No

The official spelling of GNU is GNU and not Gnu. However, the Linux kernel
documentation (including documentation included with the source code) often has
it spelled Gnu. A good example is the Changes text file in the Documentation
folder of recent source code archives. It has GNU Make spelled Gnu Make, GNU
GCC spelled Gnu GCC, etc. This may be a minhor typo )that occurs many times in
several parts of its documentation), but I think it makes Linux look
improfessional and should be fixed whenever possible.

--

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

Ma Shimiao | 10 Dec 09:50 2014

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

The function pow10(), pow10f() and pow10l() are thread safe.

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

diff --git a/man3/pow10.3 b/man3/pow10.3
index d6368fc..9a80827 100644
--- a/man3/pow10.3
+++ b/man3/pow10.3
 <at>  <at>  -46,6 +46,20  <at>  <at>  power
 .IR x .
 .SH VERSIONS
 These functions first appeared in glibc in version 2.1.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw28 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR pow10 (),
+.BR pow10f (),
+.BR pow10l ()
+T}	Thread safety	MT-Safe
+.TE
 .SH CONFORMING TO
(Continue reading)

Ma Shimiao | 10 Dec 09:40 2014

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

The function pow(), powf() and powl() are thread safe.

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

diff --git a/man3/pow.3 b/man3/pow.3
index fb31bd2..a31aaf3 100644
--- a/man3/pow.3
+++ b/man3/pow.3
 <at>  <at>  -313,6 +313,20  <at>  <at>  is set to
 An underflow floating-point exception
 .RB ( FE_UNDERFLOW )
 is raised.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw24 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR pow (),
+.BR powf (),
+.BR powl ()
+T}	Thread safety	MT-Safe
+.TE
 .SH CONFORMING TO
(Continue reading)

Ma Shimiao | 10 Dec 09:16 2014

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

The function log10(), log10f() and log10l() are thread safe.

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

diff --git a/man3/log10.3 b/man3/log10.3
index 8485f41..19d7e8f 100644
--- a/man3/log10.3
+++ b/man3/log10.3
 <at>  <at>  -86,6 +86,20  <at>  <at>  when calling these functions.

 For a discussion of the errors that can occur for these functions, see
 .BR log (3).
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw28 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR log10 (),
+.BR log10f (),
+.BR log10l ()
+T}	Thread safety	MT-Safe
+.TE
 .SH CONFORMING TO
(Continue reading)

Ma Shimiao | 10 Dec 09:08 2014

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

The function log2(), log2f() and log2l() are thread safe.

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

diff --git a/man3/log2.3 b/man3/log2.3
index febd171..e14e653 100644
--- a/man3/log2.3
+++ b/man3/log2.3
 <at>  <at>  -88,6 +88,20  <at>  <at>  For a discussion of the errors that can occur for these functions, see
 .BR log (3).
 .SH VERSIONS
 These functions first appeared in glibc in version 2.1.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw24 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR log2 (),
+.BR log2f (),
+.BR log2l ()
+T}	Thread safety	MT-Safe
+.TE
 .SH CONFORMING TO
(Continue reading)

Ma Shimiao | 10 Dec 08:50 2014

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

The function log(), logf() and logl() are thread safe.

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

diff --git a/man3/log.3 b/man3/log.3
index 96be9ef..e12c9b1 100644
--- a/man3/log.3
+++ b/man3/log.3
 <at>  <at>  -125,6 +125,20  <at>  <at>  is set to
 A divide-by-zero floating-point exception
 .RB ( FE_DIVBYZERO )
 is raised.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw24 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR log (),
+.BR logf (),
+.BR logl ()
+T}	Thread safety	MT-Safe
+.TE
 .SH CONFORMING TO
(Continue reading)

Alexey Ishchuk | 9 Dec 07:57 2014
Picon

[PATCH] Manual pages for new PCI memory access system calls

Add s390_pci_mmio_read.2 and s390_pci_mmio_write.2 manual pages for the
new PCI MMIO memory access system calls added for s390 platform.

Signed-off-by: Alexey Ishchuk <aishchuk@...>
---
 man2/s390_pci_mmio_read.2  | 85 ++++++++++++++++++++++++++++++++++++++++++++++
 man2/s390_pci_mmio_write.2 | 83 ++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 168 insertions(+)
 create mode 100644 man2/s390_pci_mmio_read.2
 create mode 100644 man2/s390_pci_mmio_write.2

diff --git a/man2/s390_pci_mmio_read.2 b/man2/s390_pci_mmio_read.2
new file mode 100644
index 0000000..16487c3
--- /dev/null
+++ b/man2/s390_pci_mmio_read.2
 <at>  <at>  -0,0 +1,85  <at>  <at> 
+.\" Copyright (c) IBM Corp. 2014
+.\" Author: Alexey Ishchuk <aishchuk@...>
+.\"
+.\" %%%LICENSE_START(GPLv2+_DOC_FULL)
+.\" This is free documentation; you can redistribute it and/or
+.\" modify it under the terms of the GNU General Public License as
+.\" published by the Free Software Foundation; either version 2 of
+.\" the License, or (at your option) any later version.
+.\"
+.\" The GNU General Public License's references to "object code"
+.\" and "executables" are to be interpreted as the output of any
+.\" document formatting or typesetting system, including
+.\" intermediate and printed output.
(Continue reading)

bugzilla | 9 Dec 00:41 2014

[Bug 89451] New: Running Chrubuntu, 14.04 LTS, messages on startup.

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

            Bug ID: 89451
           Summary: Running Chrubuntu, 14.04 LTS, messages on startup.
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
          Assignee: documentation_man-pages@...
          Reporter: nickgasser@...
        Regression: No

Created attachment 160121
  --> https://bugzilla.kernel.org/attachment.cgi?id=160121&action=edit
My screen after them.

Hi there, I recieved multiple messages about a problem with the "Mainline
Kernal". I have no idea what that means, but i figuered at the least, i should
let you guys know. I'll attach a sreenshot of the messages i recieved.

--

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

Richard Weinberger | 8 Dec 23:27 2014
Picon

Re: [CFT][PATCH 2/7] userns: Don't allow setgroups until a gid mapping has been setablished

Am 08.12.2014 um 23:25 schrieb Andy Lutomirski:
> On Mon, Dec 8, 2014 at 2:17 PM, Richard Weinberger <richard@...> wrote:
>> Am 08.12.2014 um 23:07 schrieb Eric W. Biederman:
>>>
>>> setgroups is unique in not needing a valid mapping before it can be called,
>>> in the case of setgroups(0, NULL) which drops all supplemental groups.
>>>
>>> The design of the user namespace assumes that CAP_SETGID can not actually
>>> be used until a gid mapping is established.  Therefore add a helper function
>>> to see if the user namespace gid mapping has been established and call
>>> that function in the setgroups permission check.
>>>
>>> This is part of the fix for CVE-2014-8989, being able to drop groups
>>> without privilege using user namespaces.
>>>
>>> Cc: stable@...
>>> Signed-off-by: "Eric W. Biederman" <ebiederm@...>
>>> ---
>>>  include/linux/user_namespace.h | 9 +++++++++
>>>  kernel/groups.c                | 7 ++++++-
>>>  2 files changed, 15 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/include/linux/user_namespace.h b/include/linux/user_namespace.h
>>> index e95372654f09..41cc26e5a350 100644
>>> --- a/include/linux/user_namespace.h
>>> +++ b/include/linux/user_namespace.h
>>>  <at>  <at>  -37,6 +37,15  <at>  <at>  struct user_namespace {
>>>
>>>  extern struct user_namespace init_user_ns;
>>>
(Continue reading)

Vince Weaver | 5 Dec 16:41 2014
Picon

[patch] perf_event_open.2 exclude_host/exclude_guest clarification

Hello

The PAPI developers recently ran into some issues with the various virtual 
machine related settings in the perf_event_open() system call.

What follows is what my proposed updated manpage sections look like; I'm 
hoping to get some sort of feedback about the correctness of these statements.

	exclude_hv
		If this bit is set, the count excludes events that happen in 
		the hypervisor.  This is mainly for PMUs that have 
		built-in hardware support for this feature (such as POWER;
		this setting is silently ignored on x86). 

...

	exclude_host (since Linux 3.2)
		When  conducting  measurements that include processes 
		running VM instances (i.e. have executed a KVM_RUN 
		ioctl(2) ) only  measure events happening inside a guest 
		instance.  This is only meaningful outside the guests; 
		this setting does not change counts gathered inside of a 
		guest.  Currently this functionality is x86 only.

	exclude_guest (since Linux 3.2)
		When conducting measurements that include processes 
		running VM instances  (i.e.  have executed a KVM_RUN 
		ioctl(2) ) do not measure events happening inside guest
		instances.  This is only meaningful outside the guests;  
		this setting does not change counts gathered inside of a 
(Continue reading)


Gmane