Re: [RFC][PATCH] exec: Don't wait for ptraced threads to be reaped.

From	"Robert O'Callahan" <robert@ocallahan.org>
Newsgroups	linux.kernel
Subject	Re: [RFC][PATCH] exec: Don't wait for ptraced threads to be reaped.
Date	2017-09-04 05:20 +0200
Message-ID	<ulQ5A-9b-3@gated-at.bofh.it> (permalink)
References	(7 earlier) <th1Qe-6jM-15@gated-at.bofh.it> <thllT-3Un-7@gated-at.bofh.it> <tqDtg-3qZ-17@gated-at.bofh.it> <trQop-2Lx-1@gated-at.bofh.it> <trV4J-5Uv-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Sorry about replying to this old thread, but...

On Mon, Apr 3, 2017 at 9:07 AM, Eric W. Biederman <ebiederm@xmission.com> wrote:
> I don't know who actually useses PTRACE_O_TRACEEXIT so I don't actually
> know what the implications of changing it are.  Let's see...
>
> gdb - no
> upstart - no
> lldb - yes
> strace - no

For the record, rr uses PTRACE_O_TRACEEXIT.

When a thread exits we need to examine its address space to find its
robust futex list and record the changes that will be performed by the
kernel as it cleans up that list. So, any failures to deliver
PTRACE_EVENT_EXIT are potentially problematic for us because we won't
get a chance to examine the address space before it disappears.

Rob
-- 
lbir ye,ea yer.tnietoehr  rdn rdsme,anea lurpr  edna e hnysnenh hhe uresyf toD
selthor  stor  edna  siewaoeodm  or v sstvr  esBa  kbvted,t rdsme,aoreseoouoto
o l euetiuruewFa  kbn e hnystoivateweh uresyf tulsa rehr  rdm  or rnea lurpr
.a war hsrer holsa rodvted,t  nenh hneireseoouot.tniesiewaoeivatewt sstvr  esn

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [RFC][PATCH] exec: Don't wait for ptraced threads to be reaped. "Robert O'Callahan" <robert@ocallahan.org> - 2017-09-04 05:20 +0200

csiph-web