Release plans?

Denys Vlasenko dvlasenk at
Mon Mar 12 12:26:35 UTC 2012

On 03/10/2012 11:17 PM, Dmitry V. Levin wrote:
> On Thu, Feb 09, 2012 at 07:38:27PM +0100, Denys Vlasenko wrote:
>> On 02/09/2012 05:29 PM, Dmitry V. Levin wrote:
>>> But I'd like to hear from Denys about PTRACE_SEIZE perspective first.
>>> We surely won't release PTRACE_SEIZE_DEVEL code enabled by default because
>>> the kernel API might change.
>> I'm going to ask kernel people to drop PTRACE_SEIZE_DEVEL.
> The patch was submitted in February, but current v3.3-rc6-240-gc7b2855
> still insists on PTRACE_SEIZE_DEVEL.  Is there a prospect to release
> without PTRACE_SEIZE_DEVEL any time soon, or should we rather leave this
> experimental code disabled in the next release?

It's in linux-next git:

commit fe948360bf475b705c021fc9ba8ee3992c5d0d67
Author: Denys Vlasenko <vda.linux at>
Date:   Tue Mar 6 11:25:31 2012 +1100

     ptrace: remove PTRACE_SEIZE_DEVEL bit

     PTRACE_SEIZE code is tested and ready for production use, remove the code
     which requires special bit in data argument to make PTRACE_SEIZE work.

     Strace team prepares for a new release of strace, and we would like to
     ship the code which uses PTRACE_SEIZE, preferably after this change goes
     into released kernel.

     Signed-off-by: Denys Vlasenko <vda.linux at>
     Acked-by: Tejun Heo <tj at>
     Acked-by: Oleg Nesterov <oleg at>
     Cc: Pedro Alves <palves at>
     Cc: Jan Kratochvil <jan.kratochvil at>
     Signed-off-by: Andrew Morton <akpm at>

Looks like this change will go into linux-3.4


More information about the Strace-devel mailing list