public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Fremlin <chief@bandits.org>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [new PATCH] Re: 8139too: defunct threads
Date: 16 Apr 2001 20:42:00 +0100	[thread overview]
Message-ID: <m2u23ows1j.fsf@boreas.yi.org.> (raw)
In-Reply-To: <Pine.LNX.4.33.0104150100210.13758-100000@dystopia.lab43.org> <3AD99CE4.E1ED7090@colorfullife.com> <3ADB2522.6A0C579C@uow.edu.au>
In-Reply-To: Andrew Morton's message of "Mon, 16 Apr 2001 10:00:18 -0700"

 Andrew Morton <andrewm@uow.edu.au> writes:

[...]

> None of these will work.  The problems with globally setting
> exit_signal to SIGCHLD are that
> 
> a) If the parent does waitpid(pid, status, __WCLONE), the
>    waitpid will fail.  request_module() does this.  I don't
>    know _why_ it does this.  Maybe it's bogus.  There is no
>    explanation.

waitpid doesn't work on cloned children unless you put in __WCLONE or
__WALL, so this was necessary to catch the child at all. If you set to
use SIGCHLD this will no longer be needed (if I understand correctly).

[...]

> So it seems that we must reparent the thread to init, and
> make sure that it delivers SIGCHLD to init when it exits.

Sounds good. Why isn't SIGCHLD a stronger default anyway.

[...]

> +	/* Set the exit signal to SIGCHLD so we signal init on exit */
> +	if (this_task->exit_signal ! 0) {

Tyop.

> +		printk(KERN_ERR "task `%s' exit_signal %d in daemonize()\n",
> +			this_task->comm, this_task->exit_signal);
> +	}
> +	this_task->exit_signal = SIGCHLD;
> +
> +	write_unlock_irq(&tasklist_lock);
>  }
>  
>  void __init init_idle(void)
> 

-- 

	http://www.penguinpowered.com/~vii

  reply	other threads:[~2001-04-16 19:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-14 14:00 8139too: defunct threads Manfred Spraul
2001-04-14 16:21 ` Rod Stewart
2001-04-14 17:33   ` [PATCH] " Manfred Spraul
2001-04-14 18:53     ` Alan Cox
2001-04-14 21:43       ` Manfred Spraul
2001-04-15  5:08         ` Rod Stewart
2001-04-15 13:06           ` [new PATCH] " Manfred Spraul
2001-04-15 22:01             ` Rod Stewart
2001-04-16 17:00             ` Andrew Morton
2001-04-16 19:42               ` John Fremlin [this message]
2001-04-16 19:59                 ` Andrew Morton
2001-04-14 23:29       ` [PATCH] " Andreas Ferber

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=m2u23ows1j.fsf@boreas.yi.org. \
    --to=chief@bandits.org \
    --cc=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    /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