Sasnett_Karen | 1 Jul 13:53 2015

(unknown)


Haben Sie einen Investor brauchen?

Haben Sie geschäftliche oder persönliche Darlehen benötigen?

Wir geben Darlehen an eine natürliche Person und Unternehmen bei 3% Zinsen jährlich. Weitere
Informationen Kontaktieren Sie uns per E-Mail: omfcreditspa@...<mailto:omfcreditspa@...>

HINWEIS: Leiten Sie Ihre Antwort nur an diese E-Mail: omfcreditspa <at> hotmail.com<mailto:omfcreditspa@...>
--
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

Ambrose Feinstein | 1 Jul 02:09 2015
Picon

mmap(MAP_NORESERVE) and SIGSEGV on OOM

http://man7.org/linux/man-pages/man2/mmap.2.html says of MAP_NORESERVE

> When swap space is not reserved one might get SIGSEGV upon a write if
> no physical memory is available.

I think this sentence should be removed, or perhaps qualified with
specific circumstances or past kernel versions.  It likely descends
from documentation for some other operating system with different
behavior, but as best I can tell from reading the kernel sources and
experimenting, it does not describe Linux.

In Linux, the effect of MAP_NORESERVE is only to set VM_NORESERVE in
the vma flags, exempting the mapping from the "heuristic overcommit"
accounting; it doesn't affect the fault path.  And I know of no
out-of-memory situation in which the kernel generates SIGSEGV.  The
closest I can see is touching a MAP_SHARED region backed by a full
tmpfs, which generates SIGBUS.  For anonymous mappings the kernel
invokes the OOM killer.

The man page later hedges

> BUGS
>
> On Linux there are no guarantees like those suggested above under
> MAP_NORESERVE.

Perhaps this is meant to negate the SIGSEGV remark, but it seems more
meant for the previous sentence which actually contains the word
"guarantee".  "One might get SIGSEGV" doesn't sound like any sort of
guarantee to me.
(Continue reading)

bugzilla | 25 Jun 11:57 2015

[Bug 100471] New: cgroups' memory documentation is oudated

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

            Bug ID: 100471
           Summary: cgroups' memory documentation is oudated
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
          Assignee: documentation_man-pages@...
          Reporter: renich@...
        Regression: No

There is a note that says that the Documentation/cgroups/memory.txt is
outdated.

https://www.kernel.org/doc/Documentation/cgroups/memory.txt

It would be really cool if somebody could update it.

--

-- 
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@...
More majordomo info at  http://vger.kernel.org/majordomo-info.html
(Continue reading)

Marko Myllynen | 25 Jun 09:42 2015
Picon

[PATCH] locale.5: document era keywords

Hi Michael,

this patch completes the LC_TIME section - since these era keywords are
so tightly coupled, I'm providing them as a single patch.

Based on

http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html
http://www.open-std.org/jtc1/SC22/WG20/docs/n972-14652ft.pdf
---
 man5/locale.5 | 89 +++++++++++++++++++++++++++++++++++++++++++++++++++++++----
 1 file changed, 84 insertions(+), 5 deletions(-)

diff --git a/man5/locale.5 b/man5/locale.5
index e6c1f07..22cda04 100644
--- a/man5/locale.5
+++ b/man5/locale.5
 <at>  <at>  -1067,11 +1067,6  <at>  <at>  The definition starts with the string
 in the first column.

 The following keywords are allowed:
-.\" FIXME The following LC_TIME keywords are not documented:
-.\"	era
-.\"	era_d_fmt
-.\"	era_d_t_fmt
-.\"	era_t_fmt
 .TP
 .I abday
 followed by a list of abbreviated names of the days of the week.
 <at>  <at>  -1125,6 +1120,89  <at>  <at>  followed by the appropriate time format
(Continue reading)

Marko Myllynen | 25 Jun 09:42 2015
Picon

[PATCH] locale.5: update BUGS note

Hi Michael,

let's at least update the BUGS note in locale(5), not sure is it
really needed any more at all.

---
 man5/locale.5 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/man5/locale.5 b/man5/locale.5
index 22cda04..2d29b6e 100644
--- a/man5/locale.5
+++ b/man5/locale.5
 <at>  <at>  -1321,7 +1321,9  <at>  <at>  or
 depending on whether the week and work week actually starts on Sunday or
 Monday for the locale.
 .SH BUGS
-This manual page isn't complete.
+The above
+.I LC_COLLATE
+section is not complete.
 .\" .SH AUTHOR
 .\" Jochen Hein (Hein@...)
 .SH SEE ALSO

Thanks,

--

-- 
Marko Myllynen
--
(Continue reading)

Zeng Linggang | 24 Jun 11:28 2015

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

After research, We think
* dlopen(),
* dlerror(),
* dlsym(),
* dlclose(),
* dladdr(),
* dlvsym()
are thread-safe. But, there are not
markings of them in glibc document.

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

diff --git a/man3/dlopen.3 b/man3/dlopen.3
index cb5dbf9..53d3f16 100644
--- a/man3/dlopen.3
+++ b/man3/dlopen.3
 <at>  <at>  -396,6 +396,25  <at>  <at>  provided by glibc since version 2.1,
 does the same as
 .BR dlsym ()
 but takes a version string as an additional argument.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw29 lb lb
+l l l.
(Continue reading)

'LEUNG CHEUNG' | 21 Jun 19:05 2015
Picon

Hello


I need your assistance to transfer $22,500,000.00 Dollars from Hong Kong 
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in

Zeng Linggang | 18 Jun 07:36 2015

[PATCH] clearenv.3: ATTRIBUTES: Note function that is not thread-safe

The marking matches glibc marking.
The marking of functions in glibc is:
- clearenv: MT-Unsafe const:env

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

diff --git a/man3/clearenv.3 b/man3/clearenv.3
index 7a3d57a..101fdef 100644
--- a/man3/clearenv.3
+++ b/man3/clearenv.3
 <at>  <at>  -56,6 +56,19  <at>  <at>  value on failure.
 .\" Glibc info and the Watcom C library document "a nonzero value".
 .SH VERSIONS
 Available since glibc 2.0.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lb lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR clearenv ()
+T}	Thread safety	MT-Unsafe const:env
+.TE
+
(Continue reading)

bugzilla | 18 Jun 00:34 2015

[Bug 100081] New: sll_family required for bind() on AF_PACKET socket

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

            Bug ID: 100081
           Summary: sll_family required for bind() on AF_PACKET socket
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
          Assignee: documentation_man-pages@...
          Reporter: a0vhv@...
        Regression: No

This is from "man 7 packet":
>When you send packets it is enough to specify sll_family, sll_addr, sll_halen, sll_ifindex.  The other
fields should be 0. sll_hatype and sll_pkttype are set on received packets for your information. For bind
only sll_protocol and sll_ifindex are used.

However, the last sentence is not correct. You have to specifiy sll_family for
bind() too, otherwise it will fail.

--

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

Tobias Stoeckmann | 17 Jun 22:31 2015

[patch] setsid.2: tfix

it -> its

--- man-pages-4.00/man2/setsid.2	2015-05-07 08:30:41.000000000 +0200
+++ man-pages-4.00/man2/setsid.2	2015-04-17 21:56:24.284269525 +0200
 <at>  <at>  -43,7 +43,7  <at>  <at> 
 creates a new session if the calling process is not a
 process group leader.
 The calling process is the leader of the new session
-(i.e., its session ID is made the same as it process ID).
+(i.e., its session ID is made the same as its process ID).
 The calling process also becomes
 the process group leader of a new process group in the session
 (i.e., its process group ID is made the same as it process ID).
--
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

Tycho Andersen | 17 Jun 19:42 2015

[PATCH] ptrace.2: add PTRACE_O_SUSPEND_SECCOMP flag

From: Tycho Andersen <tycho.andersen@...>

I'm assuming (although I don't know) that this will make it into 4.2; the
"since" message may need to be updated. The commit e9e3ae0b that implements
this feature is in seccomp/tip now, though.

Signed-off-by: Tycho Andersen <tycho.andersen@...>
CC: Kees Cook <keescook@...>
CC: Andy Lutomirski <luto@...>
CC: Oleg Nesterov <oleg@...>
---
 man2/ptrace.2 | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/man2/ptrace.2 b/man2/ptrace.2
index b7c514f..5dfec3b 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
 <at>  <at>  -42,6 +42,8  <at>  <at> 
 .\" 2011-09, major update by Denys Vlasenko <vda.linux@...>
 .\" 2015-01, Kees Cook <keescook@...>
 .\"    Added PTRACE_O_TRACESECCOMP, PTRACE_EVENT_SECCOMP
+.\" 2015-06, Tycho Andersen <tycho.andersen@...>
+.\"    Added PTRACE_O_SUSPEND_SECCOMP
 .\"
 .TH PTRACE 2 2015-02-21 "Linux" "Linux Programmer's Manual"
 .SH NAME
 <at>  <at>  -592,6 +594,13  <at>  <at>  The seccomp event message data (from the
 .BR SECCOMP_RET_DATA
 portion of the seccomp filter rule) can be retrieved with
(Continue reading)


Gmane