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: <20151119.120259.878540767821437922.davem@davemloft.net>
Date:	Thu, 19 Nov 2015 12:02:59 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	eric.dumazet@...il.com
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

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.
--
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