* retrans path update problem
@ 2008-05-14 8:47 Gui Jianfeng
2008-05-14 14:09 ` Vlad Yasevich
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Gui Jianfeng @ 2008-05-14 8:47 UTC (permalink / raw)
To: linux-sctp
hello everybody,
When updating retrans path(asoc->peer.retran_path), should
we update the retran path to another transport even if only the
original retrans path is active?
In the other words, i think, retrans path should always be
changed if there are more than one transport in an association.
Am i right?
--
Regards
Gui Jianfeng
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: retrans path update problem
2008-05-14 8:47 retrans path update problem Gui Jianfeng
@ 2008-05-14 14:09 ` Vlad Yasevich
2008-05-15 0:47 ` Gui Jianfeng
2008-05-15 12:38 ` Vlad Yasevich
2 siblings, 0 replies; 4+ messages in thread
From: Vlad Yasevich @ 2008-05-14 14:09 UTC (permalink / raw)
To: linux-sctp
Gui Jianfeng wrote:
> hello everybody,
> When updating retrans path(asoc->peer.retran_path), should
> we update the retran path to another transport even if only the
> original retrans path is active?
> In the other words, i think, retrans path should always be
> changed if there are more than one transport in an association.
>
> Am i right?
And we do that with sctp_assoc_update_retran_path(). If we
don't find another active transport, we'll still try set the
retran_path to the next transport in the list.
Are you asking if we should only use ACTIVE transports?
-vlad
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: retrans path update problem
2008-05-14 8:47 retrans path update problem Gui Jianfeng
2008-05-14 14:09 ` Vlad Yasevich
@ 2008-05-15 0:47 ` Gui Jianfeng
2008-05-15 12:38 ` Vlad Yasevich
2 siblings, 0 replies; 4+ messages in thread
From: Gui Jianfeng @ 2008-05-15 0:47 UTC (permalink / raw)
To: linux-sctp
Vlad Yasevich wrote:
> Gui Jianfeng wrote:
>> hello everybody,
>> When updating retrans path(asoc->peer.retran_path), should we update
>> the retran path to another transport even if only the original retrans
>> path is active?
>> In the other words, i think, retrans path should always be changed if
>> there are more than one transport in an association.
>>
>> Am i right?
>
> And we do that with sctp_assoc_update_retran_path(). If we
> don't find another active transport, we'll still try set the
> retran_path to the next transport in the list.
>
> Are you asking if we should only use ACTIVE transports?
Vlad,
I'd like to know, if the current asoc->peer.retran_path is the only active
transport in the transport list, whether we should change asoc->peer.retran_path
to another inactive one. The sctp_assoc_update_retran_path() won't change to a
inactive transport(next one) in this scenario now, is that ok?
>
> -vlad
>
>
>
--
Regards
Gui Jianfeng
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: retrans path update problem
2008-05-14 8:47 retrans path update problem Gui Jianfeng
2008-05-14 14:09 ` Vlad Yasevich
2008-05-15 0:47 ` Gui Jianfeng
@ 2008-05-15 12:38 ` Vlad Yasevich
2 siblings, 0 replies; 4+ messages in thread
From: Vlad Yasevich @ 2008-05-15 12:38 UTC (permalink / raw)
To: linux-sctp
Gui Jianfeng wrote:
> Vlad Yasevich wrote:
>> Gui Jianfeng wrote:
>>> hello everybody,
>>> When updating retrans path(asoc->peer.retran_path), should we update
>>> the retran path to another transport even if only the original retrans
>>> path is active?
>>> In the other words, i think, retrans path should always be changed if
>>> there are more than one transport in an association.
>>>
>>> Am i right?
>> And we do that with sctp_assoc_update_retran_path(). If we
>> don't find another active transport, we'll still try set the
>> retran_path to the next transport in the list.
>>
>> Are you asking if we should only use ACTIVE transports?
>
> Vlad,
> I'd like to know, if the current asoc->peer.retran_path is the only active
> transport in the transport list, whether we should change asoc->peer.retran_path
> to another inactive one. The sctp_assoc_update_retran_path() won't change to a
> inactive transport(next one) in this scenario now, is that ok?
I see now. The appears to be a bug in sctp_assoc_update_retran_path(). Even
though it attempts to change to a non-active one based on this comment,
/* We have exhausted the list, but didn't find any
* other active transports. If so, use the next
* transport.
*/
it never does, since it finds the active retran_path and just uses that again.
Feel free to fix.
-vlad
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-05-15 12:38 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-14 8:47 retrans path update problem Gui Jianfeng
2008-05-14 14:09 ` Vlad Yasevich
2008-05-15 0:47 ` Gui Jianfeng
2008-05-15 12:38 ` Vlad Yasevich
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.