From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
Serge Hallyn <serge.hallyn@ubuntu.com>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH] Make sure to wake reaper
Date: Fri, 30 Aug 2013 12:46:17 +0000 [thread overview]
Message-ID: <20130830124617.GA17147@mail.hallyn.com> (raw)
In-Reply-To: <87bo4fwyv8.fsf@xmission.com>
Quoting Eric W. Biederman (ebiederm@xmission.com):
> The thread_group_leader of any process may not be reaped until all of
> the other threads are dead. All of the other threads of a
> multi-threaded process self reap when they exit.
Ah, I see. Thanks.
Then your patch does sound like the safest solution. Haven't
tested yet (hd failure stands in my way) though I can't see
how it could not fix the bug I was seeing.
-serge
next prev parent reply other threads:[~2013-08-30 12:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 21:11 [PATCH] Make sure to wake reaper Serge Hallyn
2013-08-29 22:08 ` Eric W. Biederman
2013-08-30 0:39 ` Eric W. Biederman
2013-08-30 1:10 ` Serge E. Hallyn
2013-08-30 5:07 ` Eric W. Biederman
2013-08-30 12:46 ` Serge E. Hallyn [this message]
2013-08-30 14:42 ` Serge E. Hallyn
2013-08-31 0:30 ` [REVIEW][PATCH] pidns: Fix hang in zap_pid_ns_processes by sending a potentially extra wakeup Eric W. Biederman
2013-09-08 17:56 ` Oleg Nesterov
2013-09-08 18:01 ` free_pid() && PIDNS_HASH_ADDING Oleg Nesterov
2013-09-08 21:25 ` Eric W. Biederman
2013-09-09 15:15 ` Oleg Nesterov
2013-09-09 17:54 ` Eric W. Biederman
2013-09-10 14:01 ` [PATCH 0/1] pidns: fix free_pid() to handle the first fork failure Oleg Nesterov
2013-09-10 14:01 ` [PATCH 1/1] " Oleg Nesterov
[not found] ` <CALkWK0kSBrN-ZHG0CEWwvjYQ86ArJtDmbKqJR_6f3_ZTN6xJQQ@mail.gmail.com>
2013-09-09 0:12 ` [REVIEW][PATCH] pidns: Fix hang in zap_pid_ns_processes by sending a potentially extra wakeup Eric W. Biederman
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=20130830124617.GA17147@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=serge.hallyn@ubuntu.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