linux-kernel - Re: [PATCH 2/5] ptrace: implement PTRACE

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 18 Jun 2011 11:04:31 +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 10:57:02AM +0200, Denys Vlasenko wrote:
> I explained this already. strace code is a bit complex, and adding
> more complexity so that it uses PTRACE_SEIZE if available, but PTRACE_ATTACH
> if it is not, will add some PITA.
> 
> Considering that strace does not want PTRACE_SEIZE per se, it only wants
> to have a way to properly see and handle group stops, having an option
> to enable *only that functonality* without having to use PTRACE_SEIZE
> will be useful for strace.

I understand that it would make strace's life somewhat easier but
don't agree the difference is significant enough to justify
introducing more options.  We're talking about small number of well
defined behaviors.  Yes, it wouldn't be as simple as adding several
liners during initialization but that doesn't warrant extra kernel
features and differing behaviors which, I think, in the long run, make
things much more complicated (not complex) than necessary.

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/