Hello! > But how can this possibly work for skb->dst'less packets (such as IPV4 > ARP generated frames)?
Consider this as an implicit argument to functions passing skbs (that's why skb->dev can be killed btw). Caller is obliged to hold reference to the device, when doing dev_queue_xmit(). The way depends on caller: IP holds dst, packet socket grabs the reference explicitly, ARP either holds a neighbour entry, when sending, or does processing in input context. Actual rule is simple: skb->dev is always implicit argument. Everyone, who queues skb, must take care of saving and protecting this argument, like all another ones. Alexey - 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
