From: Patrick McHardy <[EMAIL PROTECTED]> Date: Mon, 31 Jul 2006 20:36:58 +0200
> I'm going to do some more testing now .. Thanks for all of this work Patrick. I noticed a subtle semantic change for nf_queue(). Previously, if we can't grab the module reference for the matching entry, we'd not free the skb, return 0, and the caller tries to iterate to the next hook. That behavior is preserved for singleton frames, but that's not what happens for GSO frames. Instead, the GSO frame is split up and we always return "1" even if some of the subsegments cause __nf_queue() to return 0 due to the case described in the previous paragraph. It is, however, mindful to free up the kfree_skb so it doesn't cause a leak or anything like that. Does this matter? - 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
