From: Andrea Arcangeli <andrea@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>,
linas@austin.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Race in 2.6.0-test2 timer code
Date: Wed, 30 Jul 2003 10:37:26 +0200 [thread overview]
Message-ID: <20030730083726.GE23835@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0307300934530.433-100000@localhost.localdomain>
On Wed, Jul 30, 2003 at 09:40:14AM +0200, Ingo Molnar wrote:
>
> On Wed, 30 Jul 2003, Andrea Arcangeli wrote:
>
> > [...] I'd feel much safer with the whole timer API being smp safe w/o
> > requiring driver developers to add complicated external brainer locking.
> > This will provide a much more friendly abstraction.
>
> i agree with the goal, but your patch does not achieve this. Your patch
> does not make double-add_timer() safe for example. As far as i can see
> your 2.6 patch only introduces additional overhead.
I never did any 2.6 patch, so it maybe a different thing what you've
seen, not what I applied to 2.4. Infact even the 2.4 patch isn't from
me.
This is the fix I applied to my 2.4 tree and it definitely fixes the
problem, including add_timer against add_timer. And it fixes the bug in
practice, it usually took a few hours to crash, not it can run for days
stable and I never heard complains again.
--- linux-2.4.19.SuSE-orig/kernel/timer.c 2003-07-02 13:53:55.000000000 -0700
+++ linux-2.4.19.SuSE-timer/kernel/timer.c 2003-07-02 18:32:08.000000000 -0700
@@ -144,17 +144,22 @@ void add_timer(timer_t *timer)
CHECK_BASE(base);
CHECK_BASE(timer->base);
- spin_lock_irqsave(&base->lock, flags);
- if (timer_pending(timer))
- goto bug;
- internal_add_timer(base, timer);
- timer->base = base;
- spin_unlock_irqrestore(&base->lock, flags);
- return;
-bug:
- spin_unlock_irqrestore(&base->lock, flags);
- printk("bug: kernel timer added twice at %p.\n",
- __builtin_return_address(0));
+
+ local_irq_save(flags);
+ while (unlikely(test_and_set_bit(0, &timer->lock)))
+ while (test_bit(0, &timer->lock));
+
+ spin_lock(&base->lock);
+ if (timer_pending(timer)) {
+ printk("bug: kernel timer added twice at %p.\n",
+ __builtin_return_address(0));
+ } else {
+ internal_add_timer(base, timer);
+ timer->base = base;
+ }
+ spin_unlock(&base->lock);
+ clear_bit(0, &timer->lock);
+ local_irq_restore(flags);
}
static inline int detach_timer(timer_t *timer)
@@ -244,16 +249,24 @@ int del_timer(timer_t * timer)
CHECK_BASE(timer->base);
if (!timer->base)
return 0;
+
+ local_irq_save(flags);
+ while (unlikely(test_and_set_bit(0, &timer->lock)))
+ while (test_bit(0, &timer->lock));
+
repeat:
base = timer->base;
- spin_lock_irqsave(&base->lock, flags);
+ spin_lock(&base->lock);
if (base != timer->base) {
- spin_unlock_irqrestore(&base->lock, flags);
+ spin_unlock(&base->lock);
goto repeat;
}
ret = detach_timer(timer);
timer->list.next = timer->list.prev = NULL;
- spin_unlock_irqrestore(&base->lock, flags);
+ spin_unlock(&base->lock);
+
+ clear_bit(0, &timer->lock);
+ local_irq_restore(flags);
return ret;
}
@@ -274,34 +287,48 @@ void sync_timers(void)
int del_timer_sync(timer_t * timer)
{
+ unsigned long flags;
tvec_base_t * base;
int ret = 0;
CHECK_BASE(timer->base);
if (!timer->base)
return 0;
+
+ local_irq_save(flags);
+ while (unlikely(test_and_set_bit(0, &timer->lock)))
+ while (test_bit(0, &timer->lock));
+
for (;;) {
- unsigned long flags;
int running;
-
repeat:
base = timer->base;
- spin_lock_irqsave(&base->lock, flags);
+ spin_lock(&base->lock);
if (base != timer->base) {
- spin_unlock_irqrestore(&base->lock, flags);
+ spin_unlock(&base->lock);
goto repeat;
}
ret += detach_timer(timer);
timer->list.next = timer->list.prev = 0;
running = timer_is_running(base, timer);
- spin_unlock_irqrestore(&base->lock, flags);
+ spin_unlock(&base->lock);
if (!running)
break;
+
+ clear_bit(0, &timer->lock);
+ local_irq_restore(flags);
timer_synchronize(base, timer);
+
+ local_irq_save(flags);
+ while (unlikely(test_and_set_bit(0, &timer->lock)))
+ while (test_bit(0, &timer->lock));
}
+ clear_bit(0, &timer->lock);
+ local_irq_restore(flags);
+
return ret;
}
#endif
Andrea
next prev parent reply other threads:[~2003-07-30 8:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 15:41 PATCH: Race in 2.6.0-test2 timer code linas
2003-07-29 20:56 ` Andrew Morton
2003-07-30 5:57 ` Ingo Molnar
2003-07-30 6:36 ` Andrew Morton
2003-07-30 7:07 ` Ingo Molnar
2003-07-30 7:34 ` Andrea Arcangeli
2003-07-30 7:34 ` Ingo Molnar
2003-07-30 8:28 ` Andrea Arcangeli
2003-07-30 10:31 ` Ingo Molnar
2003-07-30 11:16 ` Andrea Arcangeli
2003-07-30 11:49 ` Ingo Molnar
2003-07-30 12:34 ` Andrea Arcangeli
2003-07-30 21:18 ` linas
2003-07-30 22:06 ` Andrea Arcangeli
2003-07-30 22:17 ` Andrea Arcangeli
2003-07-31 7:04 ` Ingo Molnar
2003-07-30 21:19 ` Andrea Arcangeli
2003-07-30 23:43 ` linas
2003-07-30 23:56 ` Andrea Arcangeli
2003-07-30 23:54 ` Andrew Morton
2003-07-31 0:16 ` Andrea Arcangeli
2003-07-31 17:23 ` linas
2003-08-01 6:27 ` Ingo Molnar
2003-07-30 7:40 ` Ingo Molnar
2003-07-30 8:37 ` Andrea Arcangeli [this message]
2003-07-30 10:34 ` Ingo Molnar
2003-07-30 10:51 ` Andrew Morton
2003-07-30 11:28 ` Andrea Arcangeli
2003-07-30 11:22 ` Andrea Arcangeli
2003-07-30 20:05 ` linas
2003-07-31 6:50 ` Ingo Molnar
2003-07-31 22:56 ` linas
2003-08-01 6:23 ` Ingo Molnar
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=20030730083726.GE23835@dualathlon.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).