netdev - Re: Add a SOCK_DESTROY operation to close sockets from userspace

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1447972270.3061531.444784113.21E95CAA@webmail.messagingengine.com>
Date:	Thu, 19 Nov 2015 23:31:10 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	Tom Herbert <tom@...bertland.com>,
	David Miller <davem@...emloft.net>,
	zenczykowski <zenczykowski@...il.com>,
	Lorenzo Colitti <lorenzo@...gle.com>,
	Stephen Hemminger <stephen@...workplumber.org>,
	Linux Kernel Network Developers <netdev@...r.kernel.org>,
	Eric Dumazet <edumazet@...gle.com>, Erik Kline <ek@...gle.com>,
	Dmitry Torokhov <dtor@...gle.com>
Subject: Re: Add a SOCK_DESTROY operation to close sockets from userspace



On Thu, Nov 19, 2015, at 23:15, Eric Dumazet wrote:
> On Thu, 2015-11-19 at 23:09 +0100, Hannes Frederic Sowa wrote:
> 
> > My point is the "eventually" and the very much increased latency until
> > the kernel learns about new better source addresses it has available. I
> > would monitor link quality over time and decide source address based on
> > this on the sending side.
> 
> We are here speaking of code running in a browser (like Chrome speaking
> to Google servers). Written in java script or whatever language du jour.
> 
> It has no business of managing routes, or interfaces.

I thought it would be necessary to support multipathing in QUIC?

Interesting and thanks,
Hannes
--
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