Re: [PATCH 1/3] ptrace.2: place GETSIGINFO and SETSIGINFO near each other

2013-08-08 Thread Andrew Vagin
Hi Michael,

On Thu, Jul 18, 2013 at 03:13:39AM +0200, Michael Kerrisk wrote:
> Thanks Andrey. Applied.

You committed one of three patches. What do you think about other
patches?

ptrace.2: add description for PTRACE_PEEKSIGINFO
ptrace.2: add description for PTRACE_{GET,SET}SIGMASK


Thanks,
Andrey

> 
> M
> 
> 
> On 07/16/13 10:19, Andrey Vagin wrote:
> > Signed-off-by: Andrey Vagin 
> > ---
> >  man2/ptrace.2 | 24 
> >  1 file changed, 12 insertions(+), 12 deletions(-)
> > 
> > diff --git a/man2/ptrace.2 b/man2/ptrace.2
> > index 0d77e3f..5fcac2b 100644
> > --- a/man2/ptrace.2
> > +++ b/man2/ptrace.2
> > @@ -255,18 +255,6 @@ On return, the kernel modifies
> >  .B iov.len
> >  to indicate the actual number of bytes returned.
> >  .TP
> > -.BR PTRACE_GETSIGINFO " (since Linux 2.3.99-pre6)"
> > -Retrieve information about the signal that caused the stop.
> > -Copy a
> > -.I siginfo_t
> > -structure (see
> > -.BR sigaction (2))
> > -from the tracee to the address
> > -.I data
> > -in the tracer.
> > -.RI ( addr
> > -is ignored.)
> > -.TP
> >  .BR PTRACE_SETREGS ", " PTRACE_SETFPREGS
> >  Modify the tracee's general-purpose or floating-point registers,
> >  respectively, from the address
> > @@ -301,6 +289,18 @@ and
> >  is analogous to
> >  .BR PTRACE_GETREGSET .
> >  .TP
> > +.BR PTRACE_GETSIGINFO " (since Linux 2.3.99-pre6)"
> > +Retrieve information about the signal that caused the stop.
> > +Copy a
> > +.I siginfo_t
> > +structure (see
> > +.BR sigaction (2))
> > +from the tracee to the address
> > +.I data
> > +in the tracer.
> > +.RI ( addr
> > +is ignored.)
> > +.TP
> >  .BR PTRACE_SETSIGINFO " (since Linux 2.3.99-pre6)"
> >  Set signal information:
> >  copy a
> > 
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH 1/3] ptrace.2: place GETSIGINFO and SETSIGINFO near each other

2013-08-08 Thread Andrew Vagin
Hi Michael,

On Thu, Jul 18, 2013 at 03:13:39AM +0200, Michael Kerrisk wrote:
 Thanks Andrey. Applied.

You committed one of three patches. What do you think about other
patches?

ptrace.2: add description for PTRACE_PEEKSIGINFO
ptrace.2: add description for PTRACE_{GET,SET}SIGMASK


Thanks,
Andrey

 
 M
 
 
 On 07/16/13 10:19, Andrey Vagin wrote:
  Signed-off-by: Andrey Vagin ava...@openvz.org
  ---
   man2/ptrace.2 | 24 
   1 file changed, 12 insertions(+), 12 deletions(-)
  
  diff --git a/man2/ptrace.2 b/man2/ptrace.2
  index 0d77e3f..5fcac2b 100644
  --- a/man2/ptrace.2
  +++ b/man2/ptrace.2
  @@ -255,18 +255,6 @@ On return, the kernel modifies
   .B iov.len
   to indicate the actual number of bytes returned.
   .TP
  -.BR PTRACE_GETSIGINFO  (since Linux 2.3.99-pre6)
  -Retrieve information about the signal that caused the stop.
  -Copy a
  -.I siginfo_t
  -structure (see
  -.BR sigaction (2))
  -from the tracee to the address
  -.I data
  -in the tracer.
  -.RI ( addr
  -is ignored.)
  -.TP
   .BR PTRACE_SETREGS ,  PTRACE_SETFPREGS
   Modify the tracee's general-purpose or floating-point registers,
   respectively, from the address
  @@ -301,6 +289,18 @@ and
   is analogous to
   .BR PTRACE_GETREGSET .
   .TP
  +.BR PTRACE_GETSIGINFO  (since Linux 2.3.99-pre6)
  +Retrieve information about the signal that caused the stop.
  +Copy a
  +.I siginfo_t
  +structure (see
  +.BR sigaction (2))
  +from the tracee to the address
  +.I data
  +in the tracer.
  +.RI ( addr
  +is ignored.)
  +.TP
   .BR PTRACE_SETSIGINFO  (since Linux 2.3.99-pre6)
   Set signal information:
   copy a
  
 
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH 1/3] ptrace.2: place GETSIGINFO and SETSIGINFO near each other

2013-07-18 Thread Michael Kerrisk
Thanks Andrey. Applied.

M


On 07/16/13 10:19, Andrey Vagin wrote:
> Signed-off-by: Andrey Vagin 
> ---
>  man2/ptrace.2 | 24 
>  1 file changed, 12 insertions(+), 12 deletions(-)
> 
> diff --git a/man2/ptrace.2 b/man2/ptrace.2
> index 0d77e3f..5fcac2b 100644
> --- a/man2/ptrace.2
> +++ b/man2/ptrace.2
> @@ -255,18 +255,6 @@ On return, the kernel modifies
>  .B iov.len
>  to indicate the actual number of bytes returned.
>  .TP
> -.BR PTRACE_GETSIGINFO " (since Linux 2.3.99-pre6)"
> -Retrieve information about the signal that caused the stop.
> -Copy a
> -.I siginfo_t
> -structure (see
> -.BR sigaction (2))
> -from the tracee to the address
> -.I data
> -in the tracer.
> -.RI ( addr
> -is ignored.)
> -.TP
>  .BR PTRACE_SETREGS ", " PTRACE_SETFPREGS
>  Modify the tracee's general-purpose or floating-point registers,
>  respectively, from the address
> @@ -301,6 +289,18 @@ and
>  is analogous to
>  .BR PTRACE_GETREGSET .
>  .TP
> +.BR PTRACE_GETSIGINFO " (since Linux 2.3.99-pre6)"
> +Retrieve information about the signal that caused the stop.
> +Copy a
> +.I siginfo_t
> +structure (see
> +.BR sigaction (2))
> +from the tracee to the address
> +.I data
> +in the tracer.
> +.RI ( addr
> +is ignored.)
> +.TP
>  .BR PTRACE_SETSIGINFO " (since Linux 2.3.99-pre6)"
>  Set signal information:
>  copy a
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [PATCH 1/3] ptrace.2: place GETSIGINFO and SETSIGINFO near each other

2013-07-18 Thread Michael Kerrisk
Thanks Andrey. Applied.

M


On 07/16/13 10:19, Andrey Vagin wrote:
 Signed-off-by: Andrey Vagin ava...@openvz.org
 ---
  man2/ptrace.2 | 24 
  1 file changed, 12 insertions(+), 12 deletions(-)
 
 diff --git a/man2/ptrace.2 b/man2/ptrace.2
 index 0d77e3f..5fcac2b 100644
 --- a/man2/ptrace.2
 +++ b/man2/ptrace.2
 @@ -255,18 +255,6 @@ On return, the kernel modifies
  .B iov.len
  to indicate the actual number of bytes returned.
  .TP
 -.BR PTRACE_GETSIGINFO  (since Linux 2.3.99-pre6)
 -Retrieve information about the signal that caused the stop.
 -Copy a
 -.I siginfo_t
 -structure (see
 -.BR sigaction (2))
 -from the tracee to the address
 -.I data
 -in the tracer.
 -.RI ( addr
 -is ignored.)
 -.TP
  .BR PTRACE_SETREGS ,  PTRACE_SETFPREGS
  Modify the tracee's general-purpose or floating-point registers,
  respectively, from the address
 @@ -301,6 +289,18 @@ and
  is analogous to
  .BR PTRACE_GETREGSET .
  .TP
 +.BR PTRACE_GETSIGINFO  (since Linux 2.3.99-pre6)
 +Retrieve information about the signal that caused the stop.
 +Copy a
 +.I siginfo_t
 +structure (see
 +.BR sigaction (2))
 +from the tracee to the address
 +.I data
 +in the tracer.
 +.RI ( addr
 +is ignored.)
 +.TP
  .BR PTRACE_SETSIGINFO  (since Linux 2.3.99-pre6)
  Set signal information:
  copy a
 

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[PATCH 1/3] ptrace.2: place GETSIGINFO and SETSIGINFO near each other

2013-07-16 Thread Andrey Vagin
Signed-off-by: Andrey Vagin 
---
 man2/ptrace.2 | 24 
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 0d77e3f..5fcac2b 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -255,18 +255,6 @@ On return, the kernel modifies
 .B iov.len
 to indicate the actual number of bytes returned.
 .TP
-.BR PTRACE_GETSIGINFO " (since Linux 2.3.99-pre6)"
-Retrieve information about the signal that caused the stop.
-Copy a
-.I siginfo_t
-structure (see
-.BR sigaction (2))
-from the tracee to the address
-.I data
-in the tracer.
-.RI ( addr
-is ignored.)
-.TP
 .BR PTRACE_SETREGS ", " PTRACE_SETFPREGS
 Modify the tracee's general-purpose or floating-point registers,
 respectively, from the address
@@ -301,6 +289,18 @@ and
 is analogous to
 .BR PTRACE_GETREGSET .
 .TP
+.BR PTRACE_GETSIGINFO " (since Linux 2.3.99-pre6)"
+Retrieve information about the signal that caused the stop.
+Copy a
+.I siginfo_t
+structure (see
+.BR sigaction (2))
+from the tracee to the address
+.I data
+in the tracer.
+.RI ( addr
+is ignored.)
+.TP
 .BR PTRACE_SETSIGINFO " (since Linux 2.3.99-pre6)"
 Set signal information:
 copy a
-- 
1.8.3.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[PATCH 1/3] ptrace.2: place GETSIGINFO and SETSIGINFO near each other

2013-07-16 Thread Andrey Vagin
Signed-off-by: Andrey Vagin ava...@openvz.org
---
 man2/ptrace.2 | 24 
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 0d77e3f..5fcac2b 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -255,18 +255,6 @@ On return, the kernel modifies
 .B iov.len
 to indicate the actual number of bytes returned.
 .TP
-.BR PTRACE_GETSIGINFO  (since Linux 2.3.99-pre6)
-Retrieve information about the signal that caused the stop.
-Copy a
-.I siginfo_t
-structure (see
-.BR sigaction (2))
-from the tracee to the address
-.I data
-in the tracer.
-.RI ( addr
-is ignored.)
-.TP
 .BR PTRACE_SETREGS ,  PTRACE_SETFPREGS
 Modify the tracee's general-purpose or floating-point registers,
 respectively, from the address
@@ -301,6 +289,18 @@ and
 is analogous to
 .BR PTRACE_GETREGSET .
 .TP
+.BR PTRACE_GETSIGINFO  (since Linux 2.3.99-pre6)
+Retrieve information about the signal that caused the stop.
+Copy a
+.I siginfo_t
+structure (see
+.BR sigaction (2))
+from the tracee to the address
+.I data
+in the tracer.
+.RI ( addr
+is ignored.)
+.TP
 .BR PTRACE_SETSIGINFO  (since Linux 2.3.99-pre6)
 Set signal information:
 copy a
-- 
1.8.3.1

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/