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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 15 Aug 2014 06:19:32 -0400 From: Neil Horman <nhorman@...driver.com> To: Eric Dumazet <eric.dumazet@...il.com> Cc: Hannes Frederic Sowa <hannes@...essinduktion.org>, Daniel Borkmann <dborkman@...hat.com>, Jesper Dangaard Brouer <brouer@...hat.com>, David Miller <davem@...emloft.net>, netdev <netdev@...r.kernel.org> Subject: Re: [RFC] packet: handle too big packets for PACKET_V3 On Thu, Aug 14, 2014 at 05:56:20PM -0700, Eric Dumazet wrote: > On Fri, 2014-08-15 at 02:50 +0200, Hannes Frederic Sowa wrote: > > > 5) Or let a setsockopt control the NETIF_F_GRO bit of an interface if it > > is bound to it? This will likely result in an implementation where we > > must count current TPACKET_V3 sockets disabling GRO on an interface, > > much like promisc counter. > > loopback interface has MTU = 64K, it looks like the problem is not tied > to GRO. > Can we add a listener to the af packet code to resize the block length of the socket based on the MTU? I realize that overloads user configuration, but if we warn them... Neil > > -- 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