netdev - Re: [PATCH] net: sctp: confirm route during forward progress

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] [day] [month] [year] [list]

Date:	Tue, 09 Jul 2013 12:50:22 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	nhorman@...driver.com
Cc:	dborkman@...hat.com, netdev@...r.kernel.org,
	linux-sctp@...r.kernel.org, vyasevich@...il.com
Subject: Re: [PATCH] net: sctp: confirm route during forward progress

From: Neil Horman <nhorman@...driver.com>
Date: Tue, 9 Jul 2013 12:23:23 -0400

> On Tue, Jul 09, 2013 at 04:17:04PM +0200, Daniel Borkmann wrote:
>> This fix has been proposed originally by Vlad Yasevich. He says:
>> 
>>   When SCTP makes forward progress (receives a SACK that acks new chunks,
>>   renegs, or answeres 0-window probes) or when HB-ACK arrives, mark
>>   the route as confirmed so we don't unnecessarily send NUD probes.
>> 
>> Having a simple SCTP client/server that exchange data chunks every 1sec,
>> without this patch ARP requests are sent periodically every 40-60sec.
>> With this fix applied, an ARP request is only done once right at the
>> "session" beginning. Also, when clearing the related ARP cache entry
>> manually during the session, a new request is correctly done. I have
>> only "backported" this to net-next and tested that it works, so full
>> credit goes to Vlad.
>> 
>> Signed-off-by: Vlad Yasevich <vyasevich@...il.com>
>> Signed-off-by: Daniel Borkmann <dborkman@...hat.com>
> Acked-by: Neil Horman <nhorman@...driver.com>

Applied, 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