netdev - Re: [RFC PATCH] sctp: Don't lookup dst if transport dst is still valid

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: <20130712.155808.2237731776440357524.davem@redhat.com>
Date:	Fri, 12 Jul 2013 15:58:08 -0700 (PDT)
From:	David Miller <davem@...hat.com>
To:	fan.du@...driver.com
Cc:	vyasevich@...il.com, nhorman@...driver.com,
	nicolas.dichtel@...nd.com, netdev@...r.kernel.org
Subject: Re: [RFC PATCH] sctp: Don't lookup dst if transport dst is still
 valid

From: Fan Du <fan.du@...driver.com>
Date: Fri, 12 Jul 2013 11:15:10 +0800

> But problem still arise when we attempt to delete address
> in multi-home mode, deleting an IPv6 address does not invalidate
> any dst which source address is the same at the deleted one.
> Which means sctp cannot rely on ip6_dst_check in this scenario.

I still cannot understand why this is an SCTP specific issue.

Specifically, I cannot see why address addition/deletion doesn't
cause problems for cached ipv6 routes in UDP and TCP sockets too.
--
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