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: Thu, 29 Sep 2016 16:39:21 +0100 From: James Chapman <jchapman@...alix.com> To: "R. Parameswaran" <parameswaran.r7@...il.com> Cc: David Miller <davem@...emloft.net>, kleptog@...na.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, nprachan@...cade.com, rshearma@...cade.com, dfawcus@...cade.com, stephen@...workplumber.org, acme@...hat.com, lboccass@...cade.com Subject: Re: [PATCH net v2] L2TP:Adjust intf MTU,factor underlay L3,overlay L2 On 29/09/16 03:36, R. Parameswaran wrote: > I agree that something like 2. below would be needed in the long run (it > will need some effort and redesign -e.g. how do I lookup the parent tunnel > from the socket when receiving a PMTU update, existing pointer chain runs > from tunnel to socket). >> 2) Add code to handle PMTU events that land on the UDP tunnel >> socket. Another function pointer could be added to struct udp_sock, similar to encap_rcv, such that the pmtu event could be handled by the UDP encap protocol implementation. James
Powered by blists - more mailing lists