linux-kernel - Re: [PATCH 11/11] ptrace: implement group stop notification for ptracer

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: <20110509101055.GI1661@htj.dyndns.org>
Date:	Mon, 9 May 2011 12:10:55 +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
Subject: Re: [PATCH 11/11] ptrace: implement group stop notification for
 ptracer

Hello,

On Mon, May 09, 2011 at 12:42:55AM +0200, Denys Vlasenko wrote:
> To clarify on "sticky":
> 
> Does this mean that if tracer userspace won't query PTRACE_GETSIGINFO,
> but will simply do:
> 
>                   waitid(P_PID, tracee, NULL, WSTOPPED);
>                   ptrace(PTRACE_CONT, tracee, NULL, NULL);
> 
> then kernel will generate INTERRUPT trap again and again
> (without letting tracee run) if job stop state of the tracee has changed?

Correct, it will be in infinite trap loop.

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/