[PATCH 1/2] ptrace.2: tfix

[PATCH 1/2] ptrace.2: tfix

[Jakub Wilk]

Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>

diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 1942456..395fe12 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -2085,7 +2085,7 @@ A process can
 .B PTRACE_ATTACH
 to any other process running under the same UID,
 as long as the tracee is dumpable (i.e., it did
-did not transition UIDs or start start privileged, and it has not employed
+not transition UIDs or start start privileged, and it has not employed
 the
 .BR prctl (2)
 .B PR_SET_DUMPABLE
-- 
2.6.4

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

[PATCH 2/2] futex.2: tfix

[Jakub Wilk]

Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>

diff --git a/man2/futex.2 b/man2/futex.2
index 8c6c023..7cf0d0b 100644
--- a/man2/futex.2
+++ b/man2/futex.2
@@ -516,7 +516,7 @@ unlock(A);
 If a waker thread used
 .BR FUTEX_WAKE ,
 then all waiters waiting on B would be woken up,
-and they would would all try to acquire lock A.
+and they would all try to acquire lock A.
 However, waking all of the threads in this manner would be pointless because
 all except one of the threads would immediately block on lock A again.
 By contrast, a requeue operation wakes just one waiter and moves
-- 
2.6.4

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

Re: [PATCH 1/2] ptrace.2: tfix

[Michael Kerrisk (man-pages)]

Thanks, Jakub. Applied. And see below.

On 01/04/2016 04:59 PM, Jakub Wilk wrote:
> Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
> 
> diff --git a/man2/ptrace.2 b/man2/ptrace.2
> index 1942456..395fe12 100644
> --- a/man2/ptrace.2
> +++ b/man2/ptrace.2
> @@ -2085,7 +2085,7 @@ A process can
>  .B PTRACE_ATTACH
>  to any other process running under the same UID,
>  as long as the tracee is dumpable (i.e., it did
> -did not transition UIDs or start start privileged, and it has not employed
> +not transition UIDs or start start privileged, and it has not employed

There was a second error here :-). s/start start/start/. Fixed.

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH 2/2] futex.2: tfix

[Michael Kerrisk (man-pages)]

On 01/04/2016 04:59 PM, Jakub Wilk wrote:
> Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>

Thanks, Jakub. Applied.

Cheers,

Michael

> diff --git a/man2/futex.2 b/man2/futex.2
> index 8c6c023..7cf0d0b 100644
> --- a/man2/futex.2
> +++ b/man2/futex.2
> @@ -516,7 +516,7 @@ unlock(A);
>  If a waker thread used
>  .BR FUTEX_WAKE ,
>  then all waiters waiting on B would be woken up,
> -and they would would all try to acquire lock A.
> +and they would all try to acquire lock A.
>  However, waking all of the threads in this manner would be pointless because
>  all except one of the threads would immediately block on lock A again.
>  By contrast, a requeue operation wakes just one waiter and moves
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH 1/2] ptrace.2: tfix

[Jakub Wilk]

Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
---
 man2/ptrace.2 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/man2/ptrace.2 b/man2/ptrace.2
index bd76099..0ff73fa 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -1600,7 +1600,7 @@ Note that all mentions
 apply equally to
 .BR PTRACE_SYSEMU_SINGLESTEP.
 .LP
-However, even if the tracee is was continued using
+However, even if the tracee was continued using
 .BR PTRACE_SYSCALL
 , it is not guaranteed that the next stop will be a syscall-exit-stop.
 Other possibilities are that the tracee may stop in a
@@ -1702,7 +1702,7 @@ always followed by syscall-exit-stop,
 stop, or the tracee's death;
 no other kinds of ptrace-stop can occur in between.
 However, note that seccomp stops (see below) can cause syscall-exit-stops,
-without preceeding syscall-entry-stops.
+without preceding syscall-entry-stops.
 If seccomp is in use, care needs
 to be taken not to misinterpret such stops as syscall-entry-stops.
 .LP
@@ -1781,7 +1781,7 @@ will cause syscall-exit-stops,
 the system call number may be changed and any other modified registers
 are visible to the to-be-executed system call as well).
 Note that there may be,
-but need not have been a preceeding syscall-entry-stop.
+but need not have been a preceding syscall-entry-stop.
 
 After a
 .BR PTRACE_EVENT_SECCOMP
-- 
2.10.2

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

Re: [PATCH 1/2] ptrace.2: tfix

[Michael Kerrisk (man-pages)]

On 11/27/2016 02:34 PM, Jakub Wilk wrote:
> Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>

Thanks, Jakub. Applied.

Cheers,

Michael


> ---
>  man2/ptrace.2 | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/man2/ptrace.2 b/man2/ptrace.2
> index bd76099..0ff73fa 100644
> --- a/man2/ptrace.2
> +++ b/man2/ptrace.2
> @@ -1600,7 +1600,7 @@ Note that all mentions
>  apply equally to
>  .BR PTRACE_SYSEMU_SINGLESTEP.
>  .LP
> -However, even if the tracee is was continued using
> +However, even if the tracee was continued using
>  .BR PTRACE_SYSCALL
>  , it is not guaranteed that the next stop will be a syscall-exit-stop.
>  Other possibilities are that the tracee may stop in a
> @@ -1702,7 +1702,7 @@ always followed by syscall-exit-stop,
>  stop, or the tracee's death;
>  no other kinds of ptrace-stop can occur in between.
>  However, note that seccomp stops (see below) can cause syscall-exit-stops,
> -without preceeding syscall-entry-stops.
> +without preceding syscall-entry-stops.
>  If seccomp is in use, care needs
>  to be taken not to misinterpret such stops as syscall-entry-stops.
>  .LP
> @@ -1781,7 +1781,7 @@ will cause syscall-exit-stops,
>  the system call number may be changed and any other modified registers
>  are visible to the to-be-executed system call as well).
>  Note that there may be,
> -but need not have been a preceeding syscall-entry-stop.
> +but need not have been a preceding syscall-entry-stop.
>  
>  After a
>  .BR PTRACE_EVENT_SECCOMP
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html