From: Roland McGrath <roland@redhat.com>
To: george@mvista.com
Cc: Gerd Knorr <kraxel@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] Re: 2.6.12: itimer_real timers don't survive execve() any more
Date: Fri, 5 Aug 2005 15:10:41 -0700 (PDT) [thread overview]
Message-ID: <20050805221041.D574B180988@magilla.sf.frob.com> (raw)
In-Reply-To: George Anzinger's message of Friday, 5 August 2005 08:33:24 -0700 <42F386C4.2080103@mvista.com>
> There are other concerns. Let me see if I understand this. A thread
> (other than the leader) can exec and we then need to change the
> real_timer to wake the new task which will NOT be using the same task
> struct.
That's correct. de_thread will turn the thread calling exec into the new
leader and kill off all the other threads, including the old leader. The
exec'ing thread's existing task_struct is reassigned to the PID of the
original leader.
> My looking at the code shows that the thread leader can exit and then
> stays around as a zombi until the last thread in the group exits.
That is correct.
> If an alarm comes during this wait I suspect it will wake this zombi and
> cause problems.
You are mistaken. The signal code handles process signals sent when the
leader is a zombie. The group leader sticks around with the PID that
matches the TGID, until there are no live threads with its TGID. That is
how process-wide kill can still work.
Thanks,
Roland
next prev parent reply other threads:[~2005-08-05 22:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 16:45 Gerd Knorr
2005-08-04 21:22 ` [PATCH] " George Anzinger
2005-08-04 21:34 ` Roland McGrath
2005-08-04 22:02 ` Andrew Morton
2005-08-04 22:10 ` George Anzinger
2005-08-05 8:44 ` Gerd Knorr
2005-08-05 15:33 ` George Anzinger
2005-08-05 22:10 ` Roland McGrath [this message]
2005-08-06 0:50 ` George Anzinger
2005-08-04 21:37 ` Andrew Morton
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=20050805221041.D574B180988@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=akpm@osdl.org \
--cc=george@mvista.com \
--cc=kraxel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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®