On Mon, May 27, 2013 at 3:26 PM, Rajahalme, Jarno (NSN - FI/Espoo)
<jarno.rajaha...@nsn.com> wrote:
>
> On May 24, 2013, at 19:26 , ext Jesse Gross wrote:
>
>> On Thu, May 23, 2013 at 9:41 PM, Rajahalme, Jarno (NSN - FI/Espoo)
>> <jarno.rajaha...@nsn.com> wrote:
>>>
>>> On May 23, 2013, at 20:28 , ext Jesse Gross wrote:
>>>> The upstream commit is not really right - the check should depend on
>>>> the origin of the packet, not the location in the networking stack
>>>> processing it. Most of the time these are somewhat the same but
>>>> obviously when bridging, received packets commonly go through the
>>>> transmit path. In the OVS tunnel code, we know that we are doing
>>>> bridging so I used the looser check.
>>>
>>> Any chance on backporting this? Obviously it requires Linux 3.9, but it 
>>> would be nice to have the looser check in the OVS releases that currently 
>>> go the the various distributions.
>>
>> Where do you think this would be useful to backport? I'm not aware of
>> any distributions currently shipping Linux 3.9 and when they do, it's
>> likely that they'll pull in the current version of OVS at the time.
>
> Oops, sloppy thinking on my part - what I actually wanted to know is if there 
> is any chance to get this change in Linux 3.9 to be backported to earlier 
> linux releases. As a bug fix, I suppose, as the current symptoms crash the 
> system when the warning is done for each packet.

I think it probably can be, you might just want to dig up the original
patch and ask that it be backported to the stable kernel series. If
there's a particular distribution that you're concerned about then you
want to follow up on that specifically.

Incidentally, the current behavior has existed for a long time. It
only cropped up recently because some drivers (mainly Broadcom)
started generating packets that are valid but outside the expected
range. The Broadcom driver was updated not too long ago to avoid this,
so that might be another possible solution.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to