linux-kernel - [PATCH] docs: networking: Remove VLAN_TAG

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>] [day] [month] [year] [list]

Message-ID: <20250129160625.97979-1-ak.karis@gmail.com>
Date: Wed, 29 Jan 2025 17:06:25 +0100
From: Andreas Karis <ak.karis@...il.com>
To: linux-doc@...r.kernel.org
Cc: ak.karis@...il.com,
	linux-kernel@...r.kernel.org,
	davem@...emloft.net,
	netdev@...r.kernel.org,
	corbet@....net
Subject: [PATCH] docs: networking: Remove VLAN_TAG_PRESENT from openvswitch doc

Since commit 0c4b2d370514cb4f3454dd3b18f031d2651fab73
("net: remove VLAN_TAG_PRESENT"), the kernel no longer sets the DEI/CFI
bit in __vlan_hwaccel_put_tag to indicate the presence of a VLAN tag.
Update the openvswitch documentation which still contained an outdated
reference to this mechanism.

Signed-off-by: Andreas Karis <ak.karis@...il.com>
---
 Documentation/networking/openvswitch.rst | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/Documentation/networking/openvswitch.rst b/Documentation/networking/openvswitch.rst
index 1a8353dbf1b6..5699bbadea47 100644
--- a/Documentation/networking/openvswitch.rst
+++ b/Documentation/networking/openvswitch.rst
@@ -230,11 +230,9 @@ an all-zero-bits vlan and an empty encap attribute, like this::
     eth(...), eth_type(0x8100), vlan(0), encap()
 
 Unlike a TCP packet with source and destination ports 0, an
-all-zero-bits VLAN TCI is not that rare, so the CFI bit (aka
-VLAN_TAG_PRESENT inside the kernel) is ordinarily set in a vlan
-attribute expressly to allow this situation to be distinguished.
-Thus, the flow key in this second example unambiguously indicates a
-missing or malformed VLAN TCI.
+all-zero-bits VLAN TCI is not that rare and the flow key in
+this second example cannot indicate a missing or malformed
+VLAN TCI.
 
 Other rules
 -----------
-- 
2.48.1