From: Eric Dumazet <eric.dumazet@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Benny Amorsen <benny+usenet@amorsen.dk>,
Gertjan Hofman <gertjan_hofman@yahoo.com>,
Matt Carlson <mcarlson@broadcom.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>
Subject: [PATCH] vlan: allow VLAN ID 0 to be used
Date: Mon, 26 Oct 2009 17:13:58 +0100 [thread overview]
Message-ID: <4AE5CAC6.4000604@gmail.com> (raw)
In-Reply-To: <4AE563C7.5070702@gmail.com>
Eric Dumazet a écrit :
> VLAN id 0 is not usable on current kernel because we use 16 bits in skb to
> store vlan_tci, and vlan_tci = 0 means there is no VLAN tagging.
>
>
> We could use high order bit (0x8000) to tell if vlan tagging is set or not.
>
Here is the patch I cooked that permitted VLAN 0 to be used with tg3
(and other HW accelerated vlan nics I suppose)
[PATCH] vlan: allow VLAN ID 0 to be used
We currently use a 16 bit field (vlan_tci) to store VLAN ID on a skb.
0 value is used a special value, meaning VLAN ID not set.
This forbids use of VLAN ID 0
As VLAN ID is 12 bits, we can use high order bit as a flag, and
allow VLAN ID 0
Reported-by: Gertjan Hofman <gertjan_hofman@yahoo.com>
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
diff --git a/include/linux/if_vlan.h b/include/linux/if_vlan.h
index 7ff9af1..7dfcdb5 100644
--- a/include/linux/if_vlan.h
+++ b/include/linux/if_vlan.h
@@ -105,8 +105,9 @@ static inline void vlan_group_set_device(struct vlan_group *vg,
array[vlan_id % VLAN_GROUP_ARRAY_PART_LEN] = dev;
}
-#define vlan_tx_tag_present(__skb) ((__skb)->vlan_tci)
-#define vlan_tx_tag_get(__skb) ((__skb)->vlan_tci)
+#define VLAN_TAG_PRESENT 0x8000
+#define vlan_tx_tag_present(__skb) ((__skb)->vlan_tci & VLAN_TAG_PRESENT)
+#define vlan_tx_tag_get(__skb) ((__skb)->vlan_tci & 0x7fff)
#if defined(CONFIG_VLAN_8021Q) || defined(CONFIG_VLAN_8021Q_MODULE)
extern struct net_device *vlan_dev_real_dev(const struct net_device *dev);
@@ -231,7 +232,7 @@ static inline struct sk_buff *__vlan_put_tag(struct sk_buff *skb, u16 vlan_tci)
static inline struct sk_buff *__vlan_hwaccel_put_tag(struct sk_buff *skb,
u16 vlan_tci)
{
- skb->vlan_tci = vlan_tci;
+ skb->vlan_tci = VLAN_TAG_PRESENT | vlan_tci;
return skb;
}
@@ -284,7 +285,7 @@ static inline int __vlan_hwaccel_get_tag(const struct sk_buff *skb,
u16 *vlan_tci)
{
if (vlan_tx_tag_present(skb)) {
- *vlan_tci = skb->vlan_tci;
+ *vlan_tci = vlan_tx_tag_get(skb);
return 0;
} else {
*vlan_tci = 0;
next prev parent reply other threads:[~2009-10-26 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 4:30 VLAN and ARP failure on tg3 drivers Gertjan Hofman
2009-10-26 8:20 ` Benny Amorsen
2009-10-26 8:54 ` Eric Dumazet
2009-10-26 16:13 ` Eric Dumazet [this message]
2009-10-27 0:32 ` [PATCH] vlan: allow VLAN ID 0 to be used David Miller
2009-10-27 1:34 ` Eric Dumazet
2009-10-27 1:41 ` David Miller
2009-10-27 9:52 ` Benny Amorsen
2009-10-27 10:02 ` Eric Dumazet
2009-10-28 16:13 ` Patrick McHardy
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=4AE5CAC6.4000604@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=benny+usenet@amorsen.dk \
--cc=davem@davemloft.net \
--cc=gertjan_hofman@yahoo.com \
--cc=kaber@trash.net \
--cc=mcarlson@broadcom.com \
--cc=netdev@vger.kernel.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).