From: Roland McGrath <roland@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: ptrace && task->exit_code
Date: Wed, 27 May 2009 16:21:41 -0700 (PDT) [thread overview]
Message-ID: <20090527232141.8B24DFC2BD@magilla.sf.frob.com> (raw)
In-Reply-To: Oleg Nesterov's message of Thursday, 28 May 2009 01:05:23 +0200 <20090527230523.GA10032@redhat.com>
> I didn't realize this until yesterday, but perhaps it makes sense
> to decouple ptrace && task_struct->exit_code?
I've long thought this was an attractive idea. But it seems to have lots
of complications at least as long as ptrace-wait shares so much code with
normal wait. I'd figured this might be one of the last things we clean up
after ptrace is disentangled from core data structures in most every other
way.
> This is not completely trivial, needs another short series.
I suspect it is more hassle than benefit to do this now.
I don't think it is the right priority.
> And. I spent a lot of time, but I can't see how to solve the problems
> with TASK_STOPPED tasks if we do this change.
I bet the complications of this all will be substantially different after
we change the ptrace locking. So let's not worry about it yet.
Thanks,
Roland
next prev parent reply other threads:[~2009-05-27 23:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 0:00 [RFC PATCH 7/X] ptrace: mv task->parent ptrace_task->pt_tracer Oleg Nesterov
2009-05-25 21:59 ` Oleg Nesterov
2009-05-25 22:39 ` [RFC PATCH 8/X] ptrace: introduce ptrace_tracer() helper Oleg Nesterov
2009-05-27 2:45 ` Roland McGrath
2009-05-27 21:45 ` Oleg Nesterov
2009-05-27 22:24 ` Roland McGrath
2009-05-27 2:11 ` [RFC PATCH 7/X] ptrace: mv task->parent ptrace_task->pt_tracer Roland McGrath
2009-05-27 22:41 ` Oleg Nesterov
2009-05-27 23:05 ` ptrace && task->exit_code Oleg Nesterov
2009-05-27 23:21 ` Roland McGrath [this message]
2009-05-29 19:06 ` Oleg Nesterov
2009-06-01 2:16 ` Roland McGrath
2009-05-27 23:07 ` [RFC PATCH 7/X] ptrace: mv task->parent ptrace_task->pt_tracer Roland McGrath
2009-05-27 23:59 ` Oleg Nesterov
2009-05-28 0:32 ` Roland McGrath
2009-05-28 2:54 ` Oleg Nesterov
2009-05-28 3:19 ` Roland McGrath
2009-05-28 3:35 ` Oleg Nesterov
2009-05-28 19:28 ` Roland McGrath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090527232141.8B24DFC2BD@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®