Thread (3 messages) 3 messages, 3 authors, 2025-02-02
STALE513d

[PATCH] docs: networking: Remove VLAN_TAG_PRESENT from openvswitch doc

From: Andreas Karis <hidden>
Date: 2025-01-29 16:06:56
Also in: linux-doc, lkml
Subsystem: documentation, networking [general], openvswitch, the rest · Maintainers: Jonathan Corbet, "David S. Miller", Eric Dumazet, Jakub Kicinski, Paolo Abeni, Aaron Conole, Eelco Chaudron, Ilya Maximets, Linus Torvalds

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 <redacted>
---
 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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help