On Wed, Nov 9, 2011 at 5:54 PM, Ansis Atteka wrote:
> The function flow_metadata_from_nlattrs() is very restrictive
> about the ordering and type of metadata attributes that it receives.
> This patch will change flow_metadata_from_nlattrs() behavior by
> ignoring attributes that it does not unders
The function flow_metadata_from_nlattrs() is very restrictive
about the ordering and type of metadata attributes that it receives.
This patch will change flow_metadata_from_nlattrs() behavior by
ignoring attributes that it does not understand and allowing them
to be passed in arbitrary order.
Issu
On Wed, Nov 9, 2011 at 9:18 AM, Ansis Atteka wrote:
> On Tue, Nov 8, 2011 at 4:02 PM, Jesse Gross wrote:
>> On Tue, Nov 8, 2011 at 3:11 PM, Ansis Atteka wrote:
>> > - switch (TRANSITION(prev_type, type)) {
>> > - case TRANSITION(OVS_KEY_ATTR_UNSPEC,
>> > OVS_KEY_ATTR_
On Tue, Nov 8, 2011 at 4:02 PM, Jesse Gross wrote:
> On Tue, Nov 8, 2011 at 3:11 PM, Ansis Atteka wrote:
> > The function flow_metadata_from_nlattrs() is very restrictive
> > about the ordering and type of metadata attributes that it receives.
> > This patch will change flow_metadata_from_nlattr
On Tue, Nov 8, 2011 at 3:11 PM, Ansis Atteka wrote:
> The function flow_metadata_from_nlattrs() is very restrictive
> about the ordering and type of metadata attributes that it receives.
> This patch will change flow_metadata_from_nlattrs() behavior by
> ignoring attributes that it does not unders
The function flow_metadata_from_nlattrs() is very restrictive
about the ordering and type of metadata attributes that it receives.
This patch will change flow_metadata_from_nlattrs() behavior by
ignoring attributes that it does not understand and allowing them
to be passed in arbitrary order.
Issu