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:26:06 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Indan Zupancic <indan@....nu>
Cc:	Denys Vlasenko <vda.linux@...glemail.com>,
	Tejun Heo <tj@...nel.org>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Why I want PTRACE_O_TRACESTOP option

On 09/09, Indan Zupancic wrote:
>
> It is very useful to set options atomically at SEIZE time.

Nobody argues with this.

> Another important reason to make PTRACE_O_TRACESTOP an option is
> because not everyone uses SEIZE: Users using PTRACE_TRACEME can't
> set this option at all.

Yes. This was already discussed, PTRACE_TRACEME obviously doesn't
work if you need the new features. So far it was decided TRACEME
should be avoided, but perhaps we can add SEIZE_ME. And, unlike
TRACEME it should probably stop immediately to simplify the
synchronization with parent. Afaik, any user of TRACEME does
something like kill(getpid(), SIGSTOP), this doesn't look very
good.

But personally I'd prefer to avoid SEIZE_ME.

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/