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: Sat, 18 Jun 2011 10:35:59 +0200 From: Tejun Heo <tj@...nel.org> To: Denys Vlasenko <vda.linux@...glemail.com> Cc: oleg@...hat.com, jan.kratochvil@...hat.com, linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, indan@....nu, bdonlan@...il.com, pedro@...esourcery.com Subject: Re: [PATCH 2/5] ptrace: implement PTRACE_SEIZE Hello, On Sat, Jun 18, 2011 at 09:59:38AM +0200, Denys Vlasenko wrote: > ...unless we plan to introduce PTRACE_O_TRACESTOP (with value 0x00000080) > which enables PTRACE_INTERRUPT and stop notifications independently > of PTRACE_SEIZE. Which would be very useful for e.g. strace. I know you're a big fan of those option flags but I don't really see the added value in making these behaviors optional rather than keeping things backward compatible - ie. introducing new event needed to be gated somehow so the O flags but SEIZE itself serves as a big gate anyway so I don't see much point in introducing multiple selectable behaviors. It's not like PTRACE_O_TRACESTOP is gonna make anything drastically easier or reduce significant amount of overhead. Thanks. -- tejun -- 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