From: Andrew Vagin <avagin-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Andrey Vagin <avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH 1/3] ptrace.2: place GETSIGINFO and SETSIGINFO near each other
Date: Thu, 8 Aug 2013 18:43:56 +0400 [thread overview]
Message-ID: <20130808144356.GA25148@paralelels.com> (raw)
In-Reply-To: <51E74143.4040709-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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 <avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.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-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Vagin <avagin@parallels.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Andrey Vagin <avagin@openvz.org>, <linux-man@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <criu@openvz.org>
Subject: Re: [PATCH 1/3] ptrace.2: place GETSIGINFO and SETSIGINFO near each other
Date: Thu, 8 Aug 2013 18:43:56 +0400 [thread overview]
Message-ID: <20130808144356.GA25148@paralelels.com> (raw)
In-Reply-To: <51E74143.4040709@gmail.com>
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 <avagin@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
> >
>
next prev parent reply other threads:[~2013-08-08 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 8:19 [PATCH 0/3] ptrace.2: explain new commands to work with signals Andrey Vagin
2013-07-16 8:19 ` Andrey Vagin
2013-07-16 8:19 ` [PATCH 1/3] ptrace.2: place GETSIGINFO and SETSIGINFO near each other Andrey Vagin
[not found] ` <1373962773-2041-2-git-send-email-avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2013-07-18 1:13 ` Michael Kerrisk
2013-07-18 1:13 ` Michael Kerrisk
[not found] ` <51E74143.4040709-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-08-08 14:43 ` Andrew Vagin [this message]
2013-08-08 14:43 ` Andrew Vagin
2013-07-16 8:19 ` [PATCH 2/3] ptrace.2: add description for PTRACE_PEEKSIGINFO Andrey Vagin
[not found] ` <1373962773-2041-3-git-send-email-avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-01-20 10:02 ` Michael Kerrisk (man-pages)
2014-01-20 10:02 ` Michael Kerrisk (man-pages)
2013-07-16 8:19 ` [PATCH 3/3] ptrace.2: add description for PTRACE_{GET,SET}SIGMASK Andrey Vagin
[not found] ` <1373962773-2041-4-git-send-email-avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-01-20 10:03 ` Michael Kerrisk (man-pages)
2014-01-20 10:03 ` Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130808144356.GA25148@paralelels.com \
--to=avagin-bzqdu9zft3wakbo8gow8eq@public.gmane.org \
--cc=avagin-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.