From: David Miller <davem@redhat.com>
To: fan.du@windriver.com
Cc: vyasevich@gmail.com, nhorman@tuxdriver.com,
nicolas.dichtel@6wind.com, netdev@vger.kernel.org
Subject: Re: [RFC PATCH] sctp: Don't lookup dst if transport dst is still valid
Date: Fri, 12 Jul 2013 15:58:08 -0700 (PDT) [thread overview]
Message-ID: <20130712.155808.2237731776440357524.davem@redhat.com> (raw)
In-Reply-To: <51DF74BE.6000001@windriver.com>
From: Fan Du <fan.du@windriver.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.
next prev parent reply other threads:[~2013-07-12 22:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 6:39 [RFC PATCH] sctp: Don't lookup dst if transport dst is still valid Fan Du
2013-07-02 14:29 ` Vlad Yasevich
2013-07-02 15:55 ` Neil Horman
2013-07-03 2:39 ` Fan Du
2013-07-03 13:48 ` Vlad Yasevich
2013-07-02 19:47 ` David Miller
2013-07-03 2:18 ` Fan Du
2013-07-03 13:23 ` Vlad Yasevich
2013-07-03 14:11 ` Vlad Yasevich
2013-07-04 2:33 ` Fan Du
2013-07-05 13:03 ` Neil Horman
2013-07-09 7:11 ` Fan Du
2013-07-09 11:38 ` Neil Horman
2013-07-05 14:09 ` Vlad Yasevich
2013-07-09 15:11 ` Vlad Yasevich
2013-07-10 5:26 ` Fan Du
2013-07-12 11:19 ` Neil Horman
2013-07-16 9:13 ` Fan Du
2013-07-13 12:21 ` Vlad Yasevich
2013-07-17 7:04 ` Fan Du
2013-07-12 3:15 ` Fan Du
2013-07-12 22:58 ` David Miller [this message]
2013-07-13 12:18 ` Vlad Yasevich
2013-07-16 9:58 ` Fan Du
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130712.155808.2237731776440357524.davem@redhat.com \
--to=davem@redhat.com \
--cc=fan.du@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=nicolas.dichtel@6wind.com \
--cc=vyasevich@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.