lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 3 Feb 2010 08:47:37 +0530 From: Haavard Skinnemoen <haavard.skinnemoen@...el.com> To: Christoph Hellwig <hch@....de> Cc: roland@...hat.com, oleg@...hat.com, akpm@...ux-foundation.org, hskinnemoen@...el.com, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org Subject: Re: [PATCH 4/14] avr32: use generic ptrace_resume code On Tue, 2 Feb 2010 19:58:57 +0100 Christoph Hellwig <hch@....de> wrote: > Use the generic ptrace_resume code for PTRACE_SYSCALL, PTRACE_CONT, > PTRACE_KILL and PTRACE_SINGLESTEP. This implies defining > arch_has_single_step in <asm/ptrace.h> and implementing the > user_enable_single_step and user_disable_single_step functions, which > also causes the breakpoint information to be cleared on fork, which > could be considered a bug fix. > > Also the TIF_SYSCALL_TRACE thread flag is now cleared on PTRACE_KILL > which it previously wasn't which is consistent with all architectures > using the modern ptrace code. > > Currently avr32 doesn't implement any code to disable single stepping > when one of the non-syscall requests is called which seems wrong, > but I've left it as-is for now. > > Signed-off-by: Christoph Hellwig <hch@....de> Acked-by: Haavard Skinnemoen <haavard.skinnemoen@...el.com> Sounds like you found three bugs and fixed two of them. Can you tell me more about the last one, i.e. what should be done to disable single-stepping? Haavard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists