| 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: Wed, 22 Oct 2014 12:14:18 -0400 (EDT) From: David Miller <davem@...emloft.net> To: kristian.evensen@...il.com Cc: netdev@...r.kernel.org Subject: Re: [PATCH net-next] tcp: Add TCP_FREEZE socket option From: Kristian Evensen <kristian.evensen@...il.com> Date: Wed, 22 Oct 2014 17:36:36 +0200 > This patch introduces support for Freeze-TCP [1]. By your description I would not expect the application to get involved with the actual final zero window advertisement decision at all. Instead, I would expect the device layer to trigger a notification during a "technology change" or whatever you want to call losing connectivity, whichi TCP can receive and use to start sending zero windows over all TCP connections using that path. So the socket option enables or disables the facility, but doesn't actually trigger the zero window advertisement. A real device based event does that. The application has no business watching for the loss of connectivity, and I am certain you do not want that logice in every application in order for it to take advantage of this. And therefore there should be a global option that turns this on for the entire system by default. This requires a lot more work than you have done here, you need to add all the notification handling, the logic in TCP to look at the attached route on send and trigger zero window probes if the device event has happened, etc. -- 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