netdev - Re: [PATCH net-next v2] unix: add read side socket memory accounting for dgram sockets

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: <20140226.154232.1642777813885536970.davem@davemloft.net>
Date:	Wed, 26 Feb 2014 15:42:32 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	hannes@...essinduktion.org
Cc:	netdev@...r.kernel.org, yannick@...hler.name,
	eric.dumazet@...il.com, xiyou.wangcong@...il.com, dan@...dstab.net
Subject: Re: [PATCH net-next v2] unix: add read side socket memory
 accounting for dgram sockets

From: Hannes Frederic Sowa <hannes@...essinduktion.org>
Date: Wed, 26 Feb 2014 21:21:54 +0100

> On Wed, Feb 26, 2014 at 02:55:59PM -0500, David Miller wrote:
>> I think you can safely put the 'other' sock pointer into the control
>> block.  Because when we disassociate from a peer any pending packets
>> in flight to him will be consumed/dropped, so there can't be any
>> lingering references, right?
> 
> I am afraid lingering socket references will happen if the sockets are
> used in unconnected mode.

Sigh...

Ok, let's wait for your hackbench results and work from there.
--
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