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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 22 May 2011 16:38:45 +0800
From:	Changli Gao <>
To:	Jiri Pirko <>
Cc:	Nicolas de Peslo√ľan 
	<>, Jesse Gross <>,
	David Miller <>,,,,,,,
Subject: Re: [patch net-next-2.6 v2] net: vlan: make non-hw-accel rx path
 similar to hw-accel

On Sun, May 22, 2011 at 2:29 PM, Jiri Pirko <> wrote:
> Sun, May 22, 2011 at 04:59:49AM CEST, wrote:
> <snip>
>>And because some setups may still require the skb not to be untagged,
>>may be we need the ability to re-tag the skb in some situations...
>>When a protocol handler or rx_handler is explicitly registered on a
>>net_device which expect to receive tagged skb, we should deliver
>>tagged skb to it... Arguably, this may sound incredible for the
>>general case, but may be required for not-so-special cases like
>>bridge or protocol analyzer.
> Wait, what setups/code require the skb not to be untagged? If there's
> such, it should be fixed.

For a transparent bridge with ports: eth0 and eth1, the vlan tags
need to be preserved.

Changli Gao(
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists