| 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
| ||
|
Message-ID: <20131114135543.GA14807@hmsreliant.think-freely.org> Date: Thu, 14 Nov 2013 08:55:43 -0500 From: Neil Horman <nhorman@...driver.com> To: Chang Xiangzhong <changxiangzhong@...il.com> Cc: vyasevich@...il.com, davem@...emloft.net, linux-sctp@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [PATCH] net: sctp: bug-fixing: retran_path not set properly after transports recovering (v3) On Thu, Nov 14, 2013 at 12:58:26AM +0100, Chang Xiangzhong wrote: > When a transport recovers due to the new coming sack, SCTP should > iterate all of its transport_list to locate the __two__ most recently used > transport and set to active_path and retran_path respectively. The exising > code does not find the two properly - In case of the following list: > > [most-recent] -> [2nd-most-recent] -> ... > > Both active_path and retran_path would be set to the 1st element. > > The bug happens when: > 1) multi-homing > 2) failure/partial_failure transport recovers > Both active_path and retran_path would be set to the same most-recent one, in > other words, retran_path would not take its role - an end user might not even > notice this issue. > > Signed-off-by: Chang Xiangzhong <changxiangzhong@...il.com> Acked-by: Neil Horman <nhorman@...driver.com> -- 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
Powered by blists - more mailing lists