public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Kuebel <kuebelr@email.uc.edu>
To: jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: [PATCH] 8139too reparent_to_init() race
Date: Sun, 28 Oct 2001 20:01:53 -0500	[thread overview]
Message-ID: <20011028200153.A331@cartman> (raw)

hello all,

lately i noticed this message during boot-up (when the network
interfaces were being configured) ...

"task `ifconfig' exit_signal 17 in reparent_to_init"

this happens only about 1/2 of the time.

after some digging this is what i found...
sometimes ifconfig's parent exits before ifconfig reaches
rtl8139_thread().  when this happens, ifconfig's exit_signal is set to
SIGCHLD (in forget_original_parent), because its new parent is init.
then rlt8139_thread() is reached it calls reparent_to_init(), which
complains that exit_signal is already non-zero.

basically this patch stops rtl8139_thread() from calling
reparent_to_init() when its parent is already init.

is this the right way to fix the problem?
should reparent_to_init() check that the parent is not already init?

as a budding kernel hacker i would appreciate any comment on this
change.

please, cc me on replies.  i can only handle the digest form of this
list.

thanks.
rob.

--- linux-2.4.13/drivers/net/8139too.orig.c	Sun Oct 28 18:16:48 2001
+++ linux-2.4.13/drivers/net/8139too.c	Sun Oct 28 18:18:47 2001
@@ -1654,7 +1654,8 @@
 	unsigned long timeout;
 
 	daemonize ();
-	reparent_to_init();
+	if (current->p_opptr != child_reaper)
+		reparent_to_init();
 	spin_lock_irq(&current->sigmask_lock);
 	sigemptyset(&current->blocked);
 	recalc_sigpending(current);

             reply	other threads:[~2001-10-29  1:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29  1:01 Robert Kuebel [this message]
2001-10-29  1:24 ` [PATCH] 8139too reparent_to_init() race 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=20011028200153.A331@cartman \
    --to=kuebelr@email.uc.edu \
    --cc=jgarzik@mandrakesoft.com \
    --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