Re: [PATCH] fix __mod_timer vs __run_timers deadlock.

Andrew Morton <[email protected]> writes:

> Oleg Nesterov <[email protected]> wrote:
>>
>> When __mod_timer() changes timer's base it waits for the completion
>> of timer->function. It is just stupid: the caller of __mod_timer()
>> can held locks which would prevent completion of the timer's
>> handler.
>>
>> Solution: do not change the base of the currently running timer.
>
> OK, fingers crossed.  Juergen, it would be great if you could test
> Oleg's patch sometime.

I had one more lockup yesterday but that probably was caused by
something else because Azureus is running fine for 24 hours now.

Thanks Oleg!


        Juergen

-- 
Juergen Kreileder, Blackdown Java-Linux Team
http://blog.blackdown.de/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
    • From: Benjamin Herrenschmidt <[email protected]>

• References:
  • [PATCH] fix __mod_timer vs __run_timers deadlock.
    • From: Oleg Nesterov <[email protected]>
  • Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: Mercurial 0.4b vs git patchbomb benchmark
• Next by Date: Re: 2.6.12-rc1-mm3: box hangs solid on resume from disk while resuming device drivers
• Previous by thread: Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
• Next by thread: Re: [PATCH] fix __mod_timer vs __run_timers deadlock.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]