| Message ID | 20210601123052.3887-1-boris.sukholitko@broadcom.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | net/sched: act_vlan: Fix modify to allow 0 | expand |
On Tue, Jun 01, 2021 at 03:30:49PM +0300, Boris Sukholitko wrote: > Currently vlan modification action checks existence of vlan priority by > comparing it to 0. Therefore it is impossible to modify existing vlan > tag to have priority 0. [...] > Change Log: > v3 -> v4: > - revert tcf_vlan_get_fill_size change: total size calculation may race vs dump > > v2 -> v3: > - Push assumes that the priority is being set > - tcf_vlan_get_fill_size accounts for priority existence > > v1 -> v2: > - Do not dump unset priority and fix tests accordingly > - Test for priority 0 modification Reviewed-by: Davide Caratti <dcaratti@redhat.com>
Hello: This series was applied to netdev/net-next.git (refs/heads/master): On Tue, 1 Jun 2021 15:30:49 +0300 you wrote: > Currently vlan modification action checks existence of vlan priority by > comparing it to 0. Therefore it is impossible to modify existing vlan > tag to have priority 0. > > For example, the following tc command will change the vlan id but will > not affect vlan priority: > > [...] Here is the summary with links: - [net-next,v4,1/3] net/sched: act_vlan: Fix modify to allow 0 https://git.kernel.org/netdev/net-next/c/9c5eee0afca0 - [net-next,v4,2/3] net/sched: act_vlan: No dump for unset priority https://git.kernel.org/netdev/net-next/c/8323b20f1d76 - [net-next,v4,3/3] net/sched: act_vlan: Test priority 0 modification https://git.kernel.org/netdev/net-next/c/8fd52b1f923c You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Currently vlan modification action checks existence of vlan priority by comparing it to 0. Therefore it is impossible to modify existing vlan tag to have priority 0. For example, the following tc command will change the vlan id but will not affect vlan priority: tc filter add dev eth1 ingress matchall action vlan modify id 300 \ priority 0 pipe mirred egress redirect dev eth2 The incoming packet on eth1: ethertype 802.1Q (0x8100), vlan 200, p 4, ethertype IPv4 will be changed to: ethertype 802.1Q (0x8100), vlan 300, p 4, ethertype IPv4 although the user has intended to have p == 0. The fix is to add tcfv_push_prio_exists flag to struct tcf_vlan_params and rely on it when deciding to set the priority. The same flag is used to avoid dumping unset vlan priority. Change Log: v3 -> v4: - revert tcf_vlan_get_fill_size change: total size calculation may race vs dump v2 -> v3: - Push assumes that the priority is being set - tcf_vlan_get_fill_size accounts for priority existence v1 -> v2: - Do not dump unset priority and fix tests accordingly - Test for priority 0 modification Boris Sukholitko (3): net/sched: act_vlan: Fix modify to allow 0 net/sched: act_vlan: No dump for unset priority net/sched: act_vlan: Test priority 0 modification include/net/tc_act/tc_vlan.h | 1 + net/sched/act_vlan.c | 11 +++++--- .../tc-testing/tc-tests/actions/vlan.json | 28 +++++++++++++++++-- 3 files changed, 34 insertions(+), 6 deletions(-)