From: Oleg Nesterov <oleg@redhat.com>
To: Matt Helsley <matthltc@us.ibm.com>
Cc: Grzegorz Nosek <root@localdomain.pl>,
Roland McGrath <roland@redhat.com>,
Sukadev Bhattiprolu <sukadev@us.ibm.com>,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: Testing lxc 0.6.5 in Fedora 13
Date: Fri, 26 Mar 2010 14:34:39 +0100 [thread overview]
Message-ID: <20100326133439.GA15790@redhat.com> (raw)
In-Reply-To: <20100326124619.GC3345@count0.beaverton.ibm.com>
On 03/26, Matt Helsley wrote:
>
> On Fri, Mar 26, 2010 at 01:00:28PM +0100, Oleg Nesterov wrote:
> >
> > > + ptrace_pid_vnr = nr;
> > > + if (unlikely(p->parent != p->real_parent)) {
> > > + rcu_read_lock();
> > > + ptrace_pid_vnr = task_pid_nr_ns(p, p->parent->nsproxy->pid_ns);
> >
> > Yes, this is what I meant.
> >
> > But we should not do this in do_fork().
>
> I'm puzzled. If not here, where should we do this? Or are you saying
> ptrace should take a reference to the pid,
Ah, no, sorry.
I meant tracehook_report_clone_complete should do this under "if (trace)".
And we need a helper to get the right pid, it could be used
by do_notify_parent() too, and (probably) we need more changes like this.
> > But once again. This change fixes the value in "tracee->ptrace_message == newpid",
> > but a quick grep shows that strace-4.5.19 doesn't use PTRACE_GETEVENTMSG at all.
>
> You are correct. However strace and gdb aren't necessarily the only users
> of ptrace so wouldn't it still be good to fix this?
Yes, agreed.
Oh. The only problem is utrace patches in -mm. I mean the possible textual
conflicts...
Oleg.
next prev parent reply other threads:[~2010-03-26 13:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100321195044.GA23757@megiteam.pl>
2010-03-23 21:28 ` Testing lxc 0.6.5 in Fedora 13 Matt Helsley
2010-03-24 9:25 ` Greg Kurz
2010-03-25 21:33 ` Grzegorz Nosek
2010-03-26 11:11 ` Oleg Nesterov
2010-03-26 11:32 ` Grzegorz Nosek
2010-03-26 12:00 ` Oleg Nesterov
2010-03-26 12:46 ` Matt Helsley
2010-03-26 13:34 ` Oleg Nesterov [this message]
2010-03-26 11:53 ` Matt Helsley
2010-03-26 12:45 ` Grzegorz Nosek
2010-03-26 12:54 ` Matt Helsley
2010-03-26 13:56 ` Oleg Nesterov
2010-03-26 13:47 ` Oleg Nesterov
2010-04-06 3:44 ` Roland McGrath
2010-04-06 13:53 ` Matt Helsley
2010-04-06 14:36 ` Oleg Nesterov
2010-04-06 15:17 ` Eric W. Biederman
2010-04-06 15:13 ` Eric W. Biederman
2010-04-06 15:29 ` Matt Helsley
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=20100326133439.GA15790@redhat.com \
--to=oleg@redhat.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.com \
--cc=roland@redhat.com \
--cc=root@localdomain.pl \
--cc=sukadev@us.ibm.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