Thread (1 message) 1 message, 1 author, 2016-03-22

Re: ptrace(2): wrong kernel version for PTRACE_SEIZE and others

From: Dmitry V. Levin <hidden>
Date: 2016-03-22 11:16:29

Possibly related (same subject, not in this thread)

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.


-- 
ldv

Attachments

  • (unnamed) [application/pgp-signature] 819 bytes
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help