public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: Mircea Damian <dmircea@kappa.ro>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: No one wants to help me :-(
Date: Fri, 13 Apr 2001 14:08:00 -0400	[thread overview]
Message-ID: <3AD74080.2499C032@didntduck.org> (raw)
In-Reply-To: <20010413134213.E13992@linux.kappa.ro>

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

Mircea Damian wrote:
> 
> Hello,
> 
> I was expecting to receive some replies to my last desperate messages:
> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg35446.html
> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg36591.html
> 
> My machine is dyeing in add_timer(). It seems to happen only on SMP
> machines and is something related to the network driver. For some reason
>  one of the timer lists gets broken so we (we are two people trying to
>  solve this issue) wrote a "safe" timer.c which tries to rebuild the chain
>  in case it hits a NULL pointer.
> 
> The machine is (ofcourse) slower with this patch but at least it works.
> 
> Maybe someone can see which is the real bug and fix it.
> 
> Please help!

I found (at least part of) the problem.  In detach_timer() we test if
the timer is pending.  If it is not the function does not remove the
timer from the list and returns 0.  The functions that call
detach_timer() do not check the return value and unconditionally set the
list pointers to NULL, even though the timer is still on the list. 
Patch against 2.4.3 attached, but there may be a better solution.

-- 

						Brian Gerst

[-- Attachment #2: detach_timer.diff --]
[-- Type: text/plain, Size: 953 bytes --]

diff -urN linux-2.4.3/kernel/timer.c linux/kernel/timer.c
--- linux-2.4.3/kernel/timer.c	Thu Dec 14 20:52:22 2000
+++ linux/kernel/timer.c	Fri Apr 13 13:26:08 2001
@@ -194,6 +194,7 @@
 	if (!timer_pending(timer))
 		return 0;
 	list_del(&timer->list);
+	timer->list.next = timer->list.prev = NULL;
 	return 1;
 }
 
@@ -217,7 +218,6 @@
 
 	spin_lock_irqsave(&timerlist_lock, flags);
 	ret = detach_timer(timer);
-	timer->list.next = timer->list.prev = NULL;
 	spin_unlock_irqrestore(&timerlist_lock, flags);
 	return ret;
 }
@@ -246,7 +246,6 @@
 
 		spin_lock_irqsave(&timerlist_lock, flags);
 		ret += detach_timer(timer);
-		timer->list.next = timer->list.prev = 0;
 		running = timer_is_running(timer);
 		spin_unlock_irqrestore(&timerlist_lock, flags);
 
@@ -309,7 +308,6 @@
  			data= timer->data;
 
 			detach_timer(timer);
-			timer->list.next = timer->list.prev = NULL;
 			timer_enter(timer);
 			spin_unlock_irq(&timerlist_lock);
 			fn(data);

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-13 10:42 No one wants to help me :-( Mircea Damian
2001-04-13 18:08 ` Brian Gerst [this message]
2001-04-13 22:05   ` george anzinger
  -- strict thread matches above, loose matches on Subject: below --
2001-04-13 15:53 Manfred Spraul
2001-04-13 16:35 Manfred Spraul

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=3AD74080.2499C032@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=dmircea@kappa.ro \
    --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