From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix for ptrace breakage
Date: Tue, 17 Sep 2002 02:44:29 +0900 [thread overview]
Message-ID: <87k7llsubm.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20020916160537.GA12905@nevyn.them.org>
Daniel Jacobowitz <dan@debian.org> writes:
> > > We have the tasklist lock. How can there be a race here? The parent
> > > can't detach while we're holding the tasklist lock. If there is a race
> > > with PTRACE_SETOPTIONS, then PTRACE_SETOPTIONS should take the lock.
> >
> > No. If the real parent don't change ->ptrace, it doesn't need
> > lock.
>
> I don't understand what you mean by that. Do you mean, "if it does
> change ->ptrace, it doesn't need a lock"?
Basically, only tracer can change ->ptrace of traced child. And, it
doesn't need lock. (there are some exceptions)
> > Ah, ok. I think, it's longtime (odd) behavior. And you think, it's
> > a bug. Right?
> >
> > And, both of your and old code has odd behavior. yes?
>
> Before your patch, do_notify_parent didn't get called; I think that
> perhaps it should be. I'll think about that. After your patch the
> process group will be unexpectedly orphaned, which is not now the case.
>
> Let me sit on this for a couple of hours. I'll send you an alternative
> patch to look at.
Ok. But I'll sleep soon. So, I'll look it, after having come back from
the office.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2002-09-16 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 10:56 [PATCH] Fix for ptrace breakage OGAWA Hirofumi
2002-09-16 11:23 ` Ingo Molnar
2002-09-16 11:41 ` OGAWA Hirofumi
2002-09-16 11:50 ` Ingo Molnar
2002-09-16 11:58 ` OGAWA Hirofumi
2002-09-16 12:44 ` OGAWA Hirofumi
2002-09-16 13:07 ` Daniel Jacobowitz
2002-09-16 14:28 ` OGAWA Hirofumi
2002-09-16 14:42 ` Daniel Jacobowitz
2002-09-16 15:57 ` OGAWA Hirofumi
2002-09-16 16:05 ` Daniel Jacobowitz
2002-09-16 17:44 ` OGAWA Hirofumi [this message]
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=87k7llsubm.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.