Messages in this thread | | | Subject | Re: kernel panics at google | Date | Fri, 21 Jan 2000 00:51:54 +0000 (GMT) | From | Alan Cox <> |
| |
> us). We guarantees that tp->retrans_head is still pointing to a > valid packet so right now I cant see a cause. > > Correct. There are several checks for NULL, anything which > fixes it up points it at the head of the write_queue which > by definition is not empty. > > All of this code is protected by asynchronous behavior either > by virtue of running in BH or from the user within' BH atomic > backlog processing. > > As in many cases, we still have the ugly "kfree_skb() runs > destructor in hardware IRQ context" stuff which can mess > with socket state. I've been over these paths several > times and they absoultely cannot mess with the socket > write queue, or retrans_head/send_head in any way.
Well someone appears to have unlinked the buffer on the queue. I guess the first thing to do is to print the other fields of skb, Notably print skb->prev and skb->list
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |