On Thu, May 17, 2007 at 10:49:45AM +1000, Benjamin Herrenschmidt wrote:
>
> > I do not know why sk_buff->head would be null, or
> > would be set in a racy kind of way, or why the rt patches
> > would cause this. But the evidence implicates that.
>
> Would it be possible that a locking bug in spidernet would cause it
> under some circumstances to get a stale skb pointer ?
The skb pointer should be brand-spanking new/fresh.
It is passed to spidernet by the netdev->hard_start_xmit
callback:
netdev->hard_start_xmit = &spider_net_xmit;
I'd expect that anything that hard_start_xmit() passed to
a device driver should have a fully valid skb. Locking
problems in spidernet could cause it to work with the wrong
skb; however, in this case, the skb pointer is passed
unmodified, directly to the spot where it fails.
Maybe there is some "make ip header fresh and clean on skb" call
that should have been made; if so, I don't know what it is.
--linas
-
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
