linux-kernel - Re: Why I want PTRACE_O

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:	Fri, 9 Sep 2011 18:14:59 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Denys Vlasenko <dvlasenk@...hat.com>, linux-kernel@...r.kernel.org,
	Denys Vlasenko <vda.linux@...glemail.com>
Subject: Re: Why I want PTRACE_O_TRACESTOP option

On 09/09, Tejun Heo wrote:
>
> To me, the rationale presented here almost argues against
> PTRACE_O_TRACESTOP.  :(

Personally I dislike PTRACE_O_TRACESTOP too.

And once again, this needs more (nontrivial) changes than just
s/PT_SEIZED/PTRACE_O_TRACESTOP/, the patch was wrong.

And, just for example. While this is minor, I'd like to improve
the error codes from ptrace_check_attach(). Until we drop
PTRACE_SEIZE_DEVEL we can safely do this. I don't think it makes
sense to add the new PTRACE_O for this.

And finally, I simply do not understand how it can be useful.

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/