From: Stefan Rompf <[EMAIL PROTECTED]> Date: Sun, 7 May 2006 12:13:56 +0200
> the linkwatch code can overflow on a jiffies wrap, scheduling > work with a too large delay. If the delay is >0x80000000, > internal_add_timer() seems to overflow too, hiding the bug, so > this isn't triggered too easily. What is so special about what linkwatch is doing such that it needs this kind of treatment and other similar pieces or code do not? We have all sorts of interfaces such as time_after() et el. in order to deal with wrapping issues. And furthermore using 64-bit jiffies here might not be appropriate because they are not guarenteed to be accessed atomically, nothing here prevents the upper 32-bits from being updated while we sample the lower 32-bits on 32-bit systems that will do the 64-bit jiffied load using two 32-bit loads. - 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
