| 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
| ||
|
Message-ID: <AANLkTikk=4ssOYBK8+11ydp+-Y1-B6_wd0yYb6OKcz8Z@mail.gmail.com> Date: Fri, 4 Mar 2011 17:41:21 +0100 From: Denys Vlasenko <vda.linux@...glemail.com> To: Jan Kratochvil <jan.kratochvil@...hat.com> Cc: Tejun Heo <tj@...nel.org>, Oleg Nesterov <oleg@...hat.com>, Roland McGrath <roland@...hat.com>, linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, akpm@...ux-foundation.org Subject: Re: [RFC] Proposal for ptrace improvements On Fri, Mar 4, 2011 at 5:14 PM, Jan Kratochvil <jan.kratochvil@...hat.com> wrote: > On Tue, 01 Mar 2011 23:14:14 +0100, Denys Vlasenko wrote: >> On Tue, Mar 1, 2011 at 8:06 PM, Jan Kratochvil <jan.kratochvil@...hat.com> wrote: >> > Currently it is already a problem that apps did not / do not expect the first >> > waitpid after PTRACE_ATTACH may not be SIGSTOP. >> >> That's exactly why we want to add a better alternative, which doesn't >> insert that blasted SIGSTOP. > > But it inserts blasted SIGTRAP (or some other signal) instead. Not a problem. The problem with SIGSTOP is that we race against possible real SIGSTOP. > It would be best if such PTRACE_SEIZE (similar to PTRACE_INTERRUPT) My understanding is that those are the same idea with different names. > would > guarantee the first waitpid afterwards returns the artificial signal from > PTRACE_SEIZE. Yes. -- vda -- 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