netdev - Re: [PATCH net] net: sctp: wake up all assocs if sndbuf policy is per socket

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20140408.131903.479985343376816007.davem@davemloft.net>
Date:	Tue, 08 Apr 2014 13:19:03 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	vyasevich@...il.com
Cc:	dborkman@...hat.com, netdev@...r.kernel.org,
	linux-sctp@...r.kernel.org, tgraf@...g.ch, nhorman@...driver.com
Subject: Re: [PATCH net] net: sctp: wake up all assocs if sndbuf policy is
 per socket

From: Vlad Yasevich <vyasevich@...il.com>
Date: Tue, 08 Apr 2014 13:13:46 -0400

> On 04/08/2014 12:50 PM, David Miller wrote:
>> From: Daniel Borkmann <dborkman@...hat.com>
>> Date: Tue,  8 Apr 2014 15:33:57 +0200
>> 
>>>  [ When net-next opens up again, we need to think how
>>>    we can ideally make a new list interface and simplify
>>>    both open-coded list traversals. ]
>> 
>> I don't think you need a new list interface.
>> 
>> Instead, just have a back pointer to the sctp_sk() from the asoc, then
>> you can do normal list traversals over the asocs.
> 
> We already have that, but doing so will give preference to first
> association and possibly starving the last one.
> 
> This starvation avoidance is the whole point of having a per-association
> accounting.

I see, thanks for explaining.
--
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