public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "Dmitry V. Levin" <ldv-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>,
	Patrick Donnelly
	<batrick-dP08NitdTj1Wk0Htik3J/w@public.gmane.org>,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: ptrace(2): wrong kernel version for PTRACE_SEIZE and others
Date: Mon, 28 Mar 2016 00:30:19 -0400	[thread overview]
Message-ID: <20160328043019.GW6588@vapier.lan> (raw)
In-Reply-To: <CAKgNAkg-MfedjbfFqjP7OjXuyN_akats1GJpZPfRk68TgEh8Fg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

On 28 Mar 2016 16:55, Michael Kerrisk (man-pages) wrote:
> On 23 March 2016 at 00:16, Dmitry V. Levin <ldv-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org> wrote:
> > On Fri, Mar 18, 2016 at 05:21:28PM -0400, Patrick Donnelly wrote:
> >> The ptrace(2) man page says that PTRACE_SEIZE, PTRACE_LISTEN, and
> >> PTRACE_INTERRUPT was introduced in Linux 3.4. In fact, this was added
> >> in 3.1:
> >>
> >> $ git diff v3.0 v3.1 include/linux/ptrace.h | grep SEIZE
> >> +#define PTRACE_SEIZE           0x4206
> >> +/* flags in @data for PTRACE_SEIZE */
> >> +#define PTRACE_SEIZE_DEVEL     0x80000000 /* temp flag for development */
> >
> > Yes, PTRACE_SEIZE was introduced by commit v3.1-rc1~308^2~28, but
> > it had to be used along with a temporary flag PTRACE_SEIZE_DEVEL,
> > which was removed later by commit v3.4-rc1~109^2~20.
> >
> > That is, between v3.0 and v3.4 we had a test mode of PTRACE_SEIZE API,
> > which was not compatible with the current PTRACE_SEIZE API introduced
> > in Linux 3.4.
> 
> So, it sounds like the page is good as it stands, right?

if the commented source has these details, then yes.  otherwise, might
be good to stash them in the commented block.  i don't think it should
be exposed to the user.

glancing at the source, i'm not seeing a commented block.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-03-28  4:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 21:21 ptrace(2): wrong kernel version for PTRACE_SEIZE and others Patrick Donnelly
     [not found] ` <CACh33FrJRvC-ZQkBD2DZjW-YYnqNY5iCu_DtB8x+Jz_w80tMPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-22 11:16   ` Dmitry V. Levin
     [not found]     ` <20160322111629.GA13320-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
2016-03-28  3:55       ` Michael Kerrisk (man-pages)
     [not found]         ` <CAKgNAkg-MfedjbfFqjP7OjXuyN_akats1GJpZPfRk68TgEh8Fg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-28  4:30           ` Mike Frysinger [this message]
     [not found]             ` <20160328043019.GW6588-UgUKS2FnFs9+urZeOPWqwQ@public.gmane.org>
2016-03-28  4:38               ` 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=20160328043019.GW6588@vapier.lan \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=batrick-dP08NitdTj1Wk0Htik3J/w@public.gmane.org \
    --cc=ldv-u2l5PoMzF/Vg9hUCZPvPmw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox