netdev - Re: [PATCH v2.40 2/7] odp: Allow VLAN actions after MPLS actions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Sep 2013 12:21:08 -0700
From:	Ben Pfaff <blp@...ira.com>
To:	Simon Horman <horms@...ge.net.au>
Cc:	dev@...nvswitch.org, netdev@...r.kernel.org,
	Jesse Gross <jesse@...ira.com>,
	Pravin B Shelar <pshelar@...ira.com>,
	Ravi K <rkerur@...il.com>,
	Isaku Yamahata <yamahata@...inux.co.jp>,
	Joe Stringer <joe@...d.net.nz>
Subject: Re: [PATCH v2.40 2/7] odp: Allow VLAN actions after MPLS actions

On Fri, Sep 27, 2013 at 09:18:31AM +0900, Simon Horman wrote:
> From: Joe Stringer <joe@...d.net.nz>
> 
> OpenFlow 1.2 and 1.3 differ on their handling of MPLS actions in the
> presence of VLAN tags. To allow correct behaviour to be committed in
> each situation, this patch adds a second round of VLAN tag action
> handling to commit_odp_actions(), which occurs after MPLS actions. This
> is implemented with a new field in 'struct xlate_in' called 'vlan_tci'.
> 
> When an push_mpls action is composed, the flow's current VLAN state is
> stored into xin->vlan_tci, and flow->vlan_tci is set to 0 (pop_vlan). If
> a VLAN tag is present, it is stripped; if not, then there is no change.
> Any later modifications to the VLAN state is written to xin->vlan_tci.
> When committing the actions, flow->vlan_tci is used before MPLS actions,
> and xin->vlan_tci is used afterwards. This retains the current datapath
> behaviour, but allows VLAN actions to be applied in a more flexible
> manner.
> 
> Signed-off-by: Joe Stringer <joe@...d.net.nz>
> Signed-off-by: Simon Horman <horms@...ge.net.au>

The commit message talks about handling OpenFlow 1.2 and 1.3 both
properly, but I don't see how the code distinguishes between the cases.
Can you explain?  Maybe this is something added in a later patch, in
which case it would be nice to mention that in the commit message.

There seems to be a typo in the comment in vlan_tci_restore() here:
> +    /* If MPLS actions were executed after MPLS, copy the final vlan_tci out
> +     * and restore the intermediate VLAN state. */

I was a little confused by the new local variable 'vlan_tci' in
do_xlate_actions().  Partly this was because the fact that I didn't find
it obvious that sometimes it points to different VLAN tags.  I think
this would be easier to see if it were initially assigned just under the
big comment rather than in an initializer, so that one would know to
look at the comment.

Thanks,

Ben.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html