From: Boris Sukholitko <boris.sukholitko@broadcom.com> To: netdev@vger.kernel.org, Jamal Hadi Salim <jhs@mojatatu.com>, Jiri Pirko <jiri@resnulli.us>, Cong Wang <xiyou.wangcong@gmail.com> Cc: linux-kselftest@vger.kernel.org, shuah@kernel.org, Ilya Lifshits <ilya.lifshits@broadcom.com>, Shmulik Ladkani <shmulik.ladkani@gmail.com>, Jakub Kicinski <kuba@kernel.org>, Davide Caratti <dcaratti@redhat.com>, Boris Sukholitko <boris.sukholitko@broadcom.com> Subject: [PATCH net-next v3 0/3] net/sched: act_vlan: Fix modify to allow 0 Date: Sun, 30 May 2021 14:40:49 +0300 [thread overview] Message-ID: <20210530114052.16483-1-boris.sukholitko@broadcom.com> (raw) [-- Attachment #1: Type: text/plain, Size: 1445 bytes --] 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: 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 | 26 ++++++++++++----- .../tc-testing/tc-tests/actions/vlan.json | 28 +++++++++++++++++-- 3 files changed, 46 insertions(+), 9 deletions(-) -- 2.29.3 [-- Attachment #2: S/MIME Cryptographic Signature --] [-- Type: application/pkcs7-signature, Size: 4221 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Boris Sukholitko <boris.sukholitko@broadcom.com> To: netdev@vger.kernel.org, Jamal Hadi Salim <jhs@mojatatu.com>, Jiri Pirko <jiri@resnulli.us>, Cong Wang <xiyou.wangcong@gmail.com> Cc: linux-kselftest@vger.kernel.org, shuah@kernel.org, Ilya Lifshits <ilya.lifshits@broadcom.com>, Shmulik Ladkani <shmulik.ladkani@gmail.com>, Jakub Kicinski <kuba@kernel.org>, Davide Caratti <dcaratti@redhat.com>, Boris Sukholitko <boris.sukholitko@broadcom.com> Subject: [PATCH net-next v3 0/3] net/sched: act_vlan: Fix modify to allow 0 Date: Sun, 30 May 2021 14:40:49 +0300 [thread overview] Message-ID: <20210530114052.16483-1-boris.sukholitko@broadcom.com> (raw) [-- Attachment #1: Type: text/plain, Size: 1445 bytes --] 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: 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 | 26 ++++++++++++----- .../tc-testing/tc-tests/actions/vlan.json | 28 +++++++++++++++++-- 3 files changed, 46 insertions(+), 9 deletions(-) -- 2.29.3 [-- Attachment #2: S/MIME Cryptographic Signature --] [-- Type: application/pkcs7-signature, Size: 4221 bytes --]
next reply other threads:[~2021-05-30 11:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-30 11:40 Boris Sukholitko [this message] 2021-05-30 11:40 ` [PATCH net-next v3 0/3] net/sched: act_vlan: Fix modify to allow 0 Boris Sukholitko 2021-05-30 11:40 ` [PATCH net-next v3 1/3] " Boris Sukholitko 2021-05-30 11:40 ` [PATCH net-next v3 2/3] net/sched: act_vlan: No dump for unset priority Boris Sukholitko 2021-06-01 5:21 ` Jakub Kicinski 2021-06-01 12:35 ` Boris Sukholitko 2021-06-01 12:48 ` Davide Caratti 2021-05-30 11:40 ` [PATCH net-next v3 3/3] net/sched: act_vlan: Test priority 0 modification Boris Sukholitko 2021-05-30 11:40 ` Boris Sukholitko 2021-05-31 11:57 ` [PATCH net-next v3 0/3] net/sched: act_vlan: Fix modify to allow 0 Davide Caratti 2021-05-31 12:13 ` Jamal Hadi Salim
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210530114052.16483-1-boris.sukholitko@broadcom.com \ --to=boris.sukholitko@broadcom.com \ --cc=dcaratti@redhat.com \ --cc=ilya.lifshits@broadcom.com \ --cc=jhs@mojatatu.com \ --cc=jiri@resnulli.us \ --cc=kuba@kernel.org \ --cc=linux-kselftest@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=shmulik.ladkani@gmail.com \ --cc=shuah@kernel.org \ --cc=xiyou.wangcong@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.