public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Manfred Spraul" <manfred@colorfullife.com>
To: <stewart@dystopia.lab43.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 8139too: defunct threads
Date: Sat, 14 Apr 2001 16:00:25 +0200	[thread overview]
Message-ID: <002e01c0c4eb$5854b940$5517fea9@local> (raw)

[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

>> Ah. Of course. All (or most) kernel initialisation is
>> done by PID 1. Search for "kernel_thread" in init/main.c
>>
>> So it seems that in your setup, process 1 is not reaping
>> children, which is why this hasn't been reported before.
>> Is there something unusual about your setup?

> I found the difference which causes this. If I build my kernel with
> IP_PNP (IP: kernel level autoconfiguration) support I get a defunt
> thread for each 8139too device. If I don't build with IP_PNP
> support I don't get any, defunct ethernet threads.

Does init(8) reap children that died before it was spawned? I assume
that the defunct tasks were there _before_ init was spawned.

Perhaps init() [in linux/init/main.c] should reap all defunct tasks
before the execve("/sbin/init").

I've attached an untested patch, could you try it?

--
    Manfred


[-- Attachment #2: patch-main.dat --]
[-- Type: application/octet-stream, Size: 423 bytes --]

--- main.c	Fri Mar 30 15:42:49 2001
+++ /pub/home/manfred/main.c	Sat Apr 14 15:56:26 2001
@@ -777,6 +777,13 @@
 
 	(void) dup(0);
 	(void) dup(0);
+
+	while (waitpid(-1, (unsigned int *)0, __WALL|WNOHANG) > 0)
+		;
+	spin_lock_irq(&current->sigmask_lock);
+	flush_signals(curtask);
+	recalc_sigpending(curtask);
+	spin_lock_irq(&current->sigmask_lock);
 	
 	/*
 	 * We try each of these until one succeeds.

             reply	other threads:[~2001-04-14 14:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-14 14:00 Manfred Spraul [this message]
2001-04-14 16:21 ` 8139too: defunct threads 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
2001-04-16 19:59                 ` Andrew Morton
2001-04-14 23:29       ` [PATCH] " Andreas Ferber
  -- strict thread matches above, loose matches on Subject: below --
2001-04-12 17:58 Rod Stewart
2001-04-12 18:54 ` Andrew Morton
2001-04-12 19:32   ` Alan Cox
2001-04-12 20:18     ` Andrew Morton
2001-04-12 21:15       ` Alan Cox
2001-04-12 19:37   ` Rod Stewart
2001-04-12 20:38     ` Andrew Morton
2001-04-12 21:23       ` Rod Stewart
2001-04-12 21:30         ` Andrew Morton
2001-04-12 21:33           ` Rod Stewart
2001-04-13 20:16       ` Rod Stewart
2001-04-12 22:19 ` David Woodhouse

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='002e01c0c4eb$5854b940$5517fea9@local' \
    --to=manfred@colorfullife.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stewart@dystopia.lab43.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