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: <CALx6S36U1e14JEH1bBaJDg3xGRxtnr=7u94opFbD2M0mJhedwQ@mail.gmail.com>
Date:	Thu, 19 Nov 2015 16:15:39 -0800
From:	Tom Herbert <tom@...bertland.com>
To:	Lorenzo Colitti <lorenzo@...gle.com>
Cc:	Eric Dumazet <eric.dumazet@...il.com>,
	David Miller <davem@...emloft.net>,
	zenczykowski <zenczykowski@...il.com>,
	Hannes Frederic Sowa <hannes@...essinduktion.org>,
	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 4:09 PM, Lorenzo Colitti <lorenzo@...gle.com> wrote:
> On Fri, Nov 20, 2015 at 9:04 AM, Tom Herbert <tom@...bertland.com> wrote:
>> or to start killing connections based on some arbitrary policy when
>> under memory pressure.
>
> You mean like the OOM killer starts killing entire processes based on
> some arbitrary policy when under memory pressure? :-)

No, I mean something that kills connections where previously this did
not happen. The fact that this is done at the process level does not
justify that it is a right to at do connections. Besides, if you
really intend to do this then provide a privileged process a means to
close *any* open file descriptor in the system (why stop at TCP
sockets)!
--
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