[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140929130543.GB1839@nanopsycho.orion>
Date: Mon, 29 Sep 2014 15:05:43 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Nicolas Dichtel <nicolas.dichtel@...nd.com>
Cc: Vladislav Yasevich <vyasevic@...hat.com>, netdev@...r.kernel.org,
Patrick McHardy <kaber@...sh.net>,
Nithin Nayak Sujir <nsujir@...adcom.com>,
Michael Chan <mchan@...adcom.com>
Subject: Re: [PATCH v2 net] net: Always untag vlan-tagged traffic on input.
Mon, Sep 29, 2014 at 02:44:57PM CEST, nicolas.dichtel@...nd.com wrote:
>Le 08/08/2014 20:42, Vladislav Yasevich a écrit :
>[snip]
>>
>>The patch attempt to fix this another way. It moves the vlan header
>>stipping code out of the vlan module and always builds it into the
>>kernel network core. This way, even if vlan is not supported on
>>a virtualizatoin host, the virtual machines running on top of such
>>host will still work with VLANs enabled.
>After this patch (0d5501c1c828 ("net: Always untag vlan-tagged traffic on
>input.")), tcpdump will not be able to display the VLAN header on input path.
>Is this really intended?
I assume you are talking about the case when CONFIG_VLAN_8021Q is "n"
right? Because if it is "m" of "y" I see no change in the code.
In case of CONFIG_VLAN_8021Q is "n" the only change is that for
non-accelerated path, skb->vlan_tci is set and vlan header is stripped.
This makes the path same to accelerated path.
tcpdump should be able to cope with skb->vlan_tci
>
>
>Regards,
>Nicolas
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists