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, 19 Jun 2013 18:52:59 +0200 From: Oleg Nesterov <oleg@...hat.com> To: Pedro Alves <palves@...hat.com> Cc: Jan Kratochvil <jan.kratochvil@...hat.com>, Denys Vlasenko <dvlasenk@...hat.com>, linux-kernel@...r.kernel.org, "Dmitry V. Levin" <ldv@...linux.org> Subject: Re: [PATCH] ptrace: make PTRACE_DETACH work on non-stopped tracees. On 06/19, Pedro Alves wrote: > > On 06/19/2013 05:09 PM, Jan Kratochvil wrote: > > On Wed, 19 Jun 2013 17:15:36 +0200, Denys Vlasenko wrote: > >> CCing Jan to hear his comments from gdb side. > > PTRACE_DETACH takes a signal number in the data parameter. > What happens to if the tracer passes a non-zero signal? non-zero doesn't matter, zero is equally bad. ptrace_detach() simply does child->exit_code = data, assuming that child will look at it after resume. This is just wrong if the child is not stopped. Oleg. -- 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