From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: Add a SOCK_DESTROY operation to close sockets from userspace
Date: Thu, 19 Nov 2015 12:02:59 -0500 (EST)
Message-ID: <20151119.120259.878540767821437922.davem@davemloft.net>
References: <1447949964.22599.220.camel@edumazet-glaptop2.roam.corp.google.com>
	<20151119.113336.1788979303067913870.davem@davemloft.net>
	<1447951664.22599.230.camel@edumazet-glaptop2.roam.corp.google.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: zenczykowski@gmail.com, lorenzo@google.com,
	hannes@stressinduktion.org, stephen@networkplumber.org,
	netdev@vger.kernel.org, edumazet@google.com, ek@google.com,
	dtor@google.com
To: eric.dumazet@gmail.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([149.20.54.216]:44129 "EHLO
	shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S934060AbbKSRDC (ORCPT
	<rfc822;netdev@vger.kernel.org>); Thu, 19 Nov 2015 12:03:02 -0500
In-Reply-To: <1447951664.22599.230.camel@edumazet-glaptop2.roam.corp.google.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 19 Nov 2015 08:47:44 -0800

> So if the reaction of this is "Patch is coming from Android, must be
> yet another hack", it is quite not fair.

I have not said this.

But the attitude of that all of a sudden we must care urgently about
some Android issue they have waited as long as possible to address
upstream... that stinks.

How come our opinions and ideas about how to approach solving this
problem were not of any value two years ago?  Why?

We've waited two years, surely Android folks can wait however long it
takes to discuss this design and alternative approaches.