On Thursday 15 February 2007 03:54, Jeff Dike wrote: > On Thu, Feb 15, 2007 at 03:34:23AM +0100, Paolo 'Blaisorblade' Giarrusso wrote: > > Index: linux-2.6.git/arch/x86_64/ia32/ptrace32.c > > =================================================================== > > --- linux-2.6.git.orig/arch/x86_64/ia32/ptrace32.c > > +++ linux-2.6.git/arch/x86_64/ia32/ptrace32.c > > @@ -246,6 +246,7 @@ asmlinkage long sys32_ptrace(long reques > > case PTRACE_SINGLESTEP: > > case PTRACE_DETACH: > > case PTRACE_SYSCALL: > > + case PTRACE_OLDSETOPTIONS: > > case PTRACE_SETOPTIONS: > > case PTRACE_SET_THREAD_AREA: > > case PTRACE_GET_THREAD_AREA: > > I sent an equivalent patch in earlier today: Doh! Interesting this timing...
> Index: linux-2.6/arch/x86_64/ia32/ptrace32.c > =================================================================== > --- linux-2.6.orig/arch/x86_64/ia32/ptrace32.c > +++ linux-2.6/arch/x86_64/ia32/ptrace32.c > @@ -239,6 +239,8 @@ asmlinkage long sys32_ptrace(long reques > __u32 val; > > switch (request) { > + case PTRACE_OLDSETOPTIONS: > + request = PTRACE_SETOPTIONS; > case PTRACE_TRACEME: > case PTRACE_ATTACH: > case PTRACE_KILL: > > I change the request so that PTRACE_OLDSETOPTIONS doesn't need to > propogate any further. However, it is present in include/asm-x86_64, > so I guess that counts as being part of the x86_64 ABI. That being > the case, I guess my patch can be dropped in favor of this one. It is handled in ptrace_request, unless there are include problems. I'm going to reboot and test mine for any remaining problem. -- Inform me of my mistakes, so I can add them to my list! Paolo Giarrusso, aka Blaisorblade http://www.user-mode-linux.org/~blaisorblade Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/