[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1447955066.22599.235.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Thu, 19 Nov 2015 09:44:26 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: David Miller <davem@...emloft.net>
Cc: zenczykowski@...il.com, lorenzo@...gle.com,
hannes@...essinduktion.org, stephen@...workplumber.org,
netdev@...r.kernel.org, edumazet@...gle.com, ek@...gle.com,
dtor@...gle.com
Subject: Re: Add a SOCK_DESTROY operation to close sockets from userspace
On Thu, 2015-11-19 at 12:02 -0500, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@...il.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.
Then we are in perfect agreement.
I did not say there was a sudden urgency, sorry for the
misunderstanding.
I only know that TCP listener rewrite in 4.4 will again trigger all
these pesky Android bugs, I would like avoiding the mess I had to cope
when TIME_WAIT were merged into regular ehash established chains.
This is the major reason I worked closely with Lorenzo.
Thanks.
--
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