Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=62f99efce61024f1c645c2c574882b510c77c579
Commit:     62f99efce61024f1c645c2c574882b510c77c579
Parent:     ef3eb3e59bd5723895b2349edec98998198ef5bb
Author:     Patrick McHardy <[EMAIL PROTECTED]>
AuthorDate: Mon Jan 21 00:22:30 2008 -0800
Committer:  David S. Miller <[EMAIL PROTECTED]>
CommitDate: Mon Jan 28 15:08:27 2008 -0800

    [VLAN]: Kill useless check
    
    vlan->real_dev is always equal to the device since thats what we used
    for the lookup. It doesn't even seem worth a WARN_ON or BUG_ON.
    
    Signed-off-by: Patrick McHardy <[EMAIL PROTECTED]>
    Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
---
 net/8021q/vlan_dev.c |   18 ------------------
 1 files changed, 0 insertions(+), 18 deletions(-)

diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
index 51ce421..50d8edc 100644
--- a/net/8021q/vlan_dev.c
+++ b/net/8021q/vlan_dev.c
@@ -181,24 +181,6 @@ int vlan_skb_recv(struct sk_buff *skb, struct net_device 
*dev,
        /* Take off the VLAN header (4 bytes currently) */
        skb_pull_rcsum(skb, VLAN_HLEN);
 
-       /* Ok, lets check to make sure the device (dev) we
-        * came in on is what this VLAN is attached to.
-        */
-
-       if (dev != VLAN_DEV_INFO(skb->dev)->real_dev) {
-               rcu_read_unlock();
-
-#ifdef VLAN_DEBUG
-               printk(VLAN_DBG "%s: dropping skb: %p because came in on wrong 
device, dev: %s  real_dev: %s, skb_dev: %s\n",
-                       __FUNCTION__, skb, dev->name,
-                       VLAN_DEV_INFO(skb->dev)->real_dev->name,
-                       skb->dev->name);
-#endif
-               kfree_skb(skb);
-               stats->rx_errors++;
-               return -1;
-       }
-
        /*
         * Deal with ingress priority mapping.
         */
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to