linux-kernel - Re: [PATCH 10/10] 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: <20110520084641.GA31426@htj.dyndns.org>
Date:	Fri, 20 May 2011 10:46:41 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	jan.kratochvil@...hat.com, vda.linux@...glemail.com,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, indan@....nu, bdonlan@...il.com
Subject: Re: [PATCH 10/10] ptrace: implement group stop notification for
 ptracer

Hello, Oleg.

On Thu, May 19, 2011 at 07:13:27PM +0200, Oleg Nesterov wrote:
> OK. I still hope we can avoid this somehow. May be play with exit_code
> so that do_wait() can succeed even if the JOBCTL_TRAPPING tracee is
> running. Perhaps.

I considered that but re-trapping seemed cleaner to me.  wait(2)
already depends on retries so I don't think adding TRAPPING wait
introduces too much extra complexity.  That said, if you can come up
with something simpler, by all means.

> If only we could notify the tracer from ptrace_trap_notify... IIUC,
> this is the only problem? I mean, apart from this there is no need
> to wake up the tracee.

Yeap, correct.
ahead.

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/