| lists.openwall.net | 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 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <m17h9jp7js.fsf@fess.ebiederm.org> Date: Sat, 21 May 2011 23:34:47 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Jiri Pirko <jpirko@...hat.com> Cc: Nicolas de Pesloüan <nicolas.2p.debian@...il.com>, Jesse Gross <jesse@...ira.com>, Changli Gao <xiaosuo@...il.com>, David Miller <davem@...emloft.net>, netdev@...r.kernel.org, shemminger@...ux-foundation.org, kaber@...sh.net, fubar@...ibm.com, eric.dumazet@...il.com, andy@...yhouse.net Subject: Re: [patch net-next-2.6 v2] net: vlan: make non-hw-accel rx path similar to hw-accel Jiri Pirko <jpirko@...hat.com> writes: > Sun, May 22, 2011 at 04:59:49AM CEST, nicolas.2p.debian@...il.com 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. tcpdump on the non-vlan interface for one. Eric -- 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