linux-kernel - Re: [RFC] Proposal for ptrace improvements

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]

Message-ID: <20110302133206.GA9838@redhat.com>
Date:	Wed, 2 Mar 2011 14:32:06 +0100
From:	Oleg Nesterov <oleg@...hat.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Indan Zupancic <indan@....nu>,
	Denys Vlasenko <vda.linux@...glemail.com>,
	Roland McGrath <roland@...hat.com>, jan.kratochvil@...hat.com,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org,
	Michael Kerrisk <mtk.manpages@...glemail.com>
Subject: Re: [RFC] Proposal for ptrace improvements

On 03/02, Tejun Heo wrote:
>
> On Wed, Mar 02, 2011 at 06:07:35AM +0100, Indan Zupancic wrote:
> > I'm not sure what Denys is talking about: Currently it's impossible to
> > pass along SIGSTOP to traced processes. Quoting the ptrace manpage:
> >
> >    PTRACE_CONT
> >           Restarts  the stopped child process.  If data is nonzero and not
> >           SIGSTOP, it is interpreted as a signal to be  delivered  to  the
> >           child;  otherwise,  no  signal is delivered.
>
> AFAICS, that's not true.  SIGSTOP isn't treated differently from other
> signals in the ptrace signal delivery path.  Maybe it was true in the
> past.

Yes, this is not true. And it seems this was never true.

This is the second time this manpage confuses people in this discussion,
probably it should be fixed...

Add Michael.

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/