Re: [PATCH net-next-2.6] net/ipv4: push IP options to CB inip_fragment

From: David Miller
Date: Wed Sep 01 2010 - 17:46:46 EST


From: Eric Dumazet <eric.dumazet@xxxxxxxxx>
Date: Tue, 31 Aug 2010 07:20:31 +0200

> We could have a padding in front of struct br_input_skb_cb to make sure
> we dont overwrite IP (4|6) CB in bridge ?
>
> Something like this untested patch :

This will not help Brandan's case.

His packets are coming straight from TUN/TAP. They did not live in
the IP stack at all before hitting the bridge and then heading to
ip_fragment().

Therefore I'm inclined to agree with Herbert that we need to parse the
options explicitly before invoke ip_fragment(). We must call it with
an SKB in the state it expects, and that means with options parsing
already performed.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/