From: Kirill Korotaev <[EMAIL PROTECTED]> Date: Wed, 09 Aug 2006 13:01:32 +0400
> F.e. timer has fired on CPU2, but the handler was preeempted > by an irq before dst_lock is tried. > Meanwhile, someone on CPU1 adds an entry to gc list and > starts the timer. > If CPU2 was preempted long enough, this timer can expire > simultaneously with resuming timer handler on CPU1, arriving > exactly to the situation described. Makes sense. Patch applied, thanks. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
