Hi David: I've been flying on and off for the last two days so I only saw this now.
On Fri, Apr 14, 2006 at 08:59:27PM -0700, David S. Miller wrote: > > Herbert, as you may have noticed we found some missing > locking in sk_stream_rfree(). It could explain the > "!sk_forward_alloc" BUG() we thought was caused by e1000's > TSO implementation and the Intel folks have provided enough > datapoints to prove that it is indeed not an e1000 specific > problem. Great eyes! Yes that bug seems to have been around forever. I'll look over the patch tomorrow as right now I'm still on west-coast time :) I have one niggling doubt though as to why turning off TSO seems to cure the problem for people. Perhaps it'll become clearer tomorrow morning when I look at it again :) Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt - 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
