| 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
| ||
|
Date: Fri, 10 Jun 2011 14:12:43 +0200 From: Jiri Pirko <jpirko@...hat.com> To: Changli Gao <xiaosuo@...il.com> Cc: David Miller <davem@...emloft.net>, pratnakarlx@...il.com, ebiederm@...ssion.com, shemminger@...ux-foundation.org, greearb@...delatech.com, nicolas.2p.debian@...il.com, netdev@...r.kernel.org, kaber@...sh.net, fubar@...ibm.com, eric.dumazet@...il.com, andy@...yhouse.net, jesse@...ira.com Subject: Re: [PATCH v3] vlan: Fix the ingress VLAN_FLAG_REORDER_HDR check Fri, Jun 10, 2011 at 01:20:29PM CEST, xiaosuo@...il.com wrote: >On Fri, Jun 10, 2011 at 6:35 PM, Jiri Pirko <jpirko@...hat.com> wrote: >> Fri, Jun 10, 2011 at 11:49:27AM CEST, xiaosuo@...il.com wrote: >>> >>>For hw-accel-vlan-rx, is the headroom for this header expansion >>>reserved? I don't think so. Thanks. >> >> But this wasn't done for hw-accel-vlan-rx previously right? So why don't >> check for hw-accel-vlan-rx and don do unreorder in that case? >> > >Yes, it wasn't done before. We want to make the behaviors of >hw-accel-vlan-rx and non-hw-accel-vlan-rx are the same. Is it your >original goal of your vlan-untag patch? You are correct. I just thought that since disabling reordering will be most likely removed in near future, non-hw-accel-vlan-rx reorder disable would not be needed. > >-- >Regards, >Changli Gao(xiaosuo@...il.com) -- 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